Manually Configure webpack
and electron-builder
instead of using electron-webpack
#5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #4 . Noteworthy doesn't rely on any sophisticated features of
electron-webpack
, so it was straightforward (though laborious) to sift through the config files generated byelectron-webpack
and manually copy the bare-minimum important bits. More sophisticated functionality provided byelectron-webpack
such as hot-module-reloading is not included. The goal was to get up and running again as quickly as possible, so that I can upgrade to new major versions of Electron and TypeScript and resume working on features. If lack of HMR proves to be a frustration, I may add it back in later.I was also able to delete some hacky config code required to glue on support for SolidJS to the
electron-webpack
config. The result is a much simpler configuration file that I can actually understand and change later! Working on this also gave me an opportunity to learn more aboutwebpack
andelectron-builder
, which I had more or less treated as black boxes until now.