slashman / jsrl Goto Github PK

• The package.json::scripts is pretty gnarly
• Every script references the base webpack/webpack.config.js in the CLI, so to clean that up, maybe just move the single webpack.config.js file to the package root
• By default webpack will try to use webpack.config.js so those references can be trimmed out of package.json

I think we've talked about it on and off before over the past year or so.

Maybe it's time to aim for a directional change @slashman ?

JSRL - this existing repo. JUST contains the JSRL library (as Typescript eventually), easily exportable for importing into any project as-is without fuss. Kinda the way it was originally launched IIRC.

JSRL-forge - (or whatever it's called) another repo that USES JSRL as an import, but designed for the developer or team wishing to pull in the ready-to-publish use of JSRL

might help a lot with maintenance, since you're only either updating the library codebase or the packager / publisher repo.

Maybe give it some thought? Worth a shot?

• We're using this dependency: https://github.com/chentsulin/webpack-target-electron-renderer
• It's an older project, and during some initial tests when I removed it, it didn't seem to impact anything in the Electron build
• Cannot upgrade to Webpack 5.x until the target issue is solved

• There are still issues with concurrency for the npm run electron:* tasks
• Must be a better solution for handling the reload of any changed source files while running Electron

• Electron Forge v6 is out, and has been advertised as a "batteries included" solution for Electron
• Is this a more reliable option for local dev and packaging / distribution?
• https://www.electronjs.org/blog/forge-v6-release

Just dropping this here to track interest in any Mobile support for JSRL

• Cordova
• Ionic?