[webpack] packages all project folder instead of the .webpack folder
See original GitHub issueI can’t get electron-forge
to package a webpack build.
Whatever i do the “dir” passed to electron-packager
is my project folder.
as seen in the cli source file i tried to do electron-forge package .webpack
but still because of that line it’s always to project folder (the folder where electron is found) which is passed to electron-packager
.
So my app ends up being 400Mo and can’t run because the main file is not found.
I know see in the code that it’s normal to “package” the whole project folder. With webpack it does not really make sense. Can you guide on how to make it work correctly with webpack?
Thanks
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
[webpack] packages all project folder instead of the ... - GitHub
I can't get electron-forge to package a webpack build. Whatever i do the "dir" passed to electron-packager is my project folder.
Read more >Output Management - webpack
In general it's good practice to clean the /dist folder before each build, so that only used files will be generated. Let's take...
Read more >Public Path - webpack
It allows you to specify the base path for all the assets within your application. Use Cases. There are a few use cases...
Read more >CopyWebpackPlugin | webpack
Copies individual files or entire directories, which already exist, to the build directory. Getting Started. To begin, you'll need to install copy-webpack- ...
Read more >Configuration - webpack
dev is an online tool for creating custom webpack configurations. It allows you to select various features that will be combined and added...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
By default beta 29 brutally ignores everything other than
.webpack
and yourpackage.json
file. And we remove thedependencies
anddevDependencies
object from your package.json for extra safetyYour package will be nice and small now 👍
@MarshallOfSound To me living the scripts seems like an Intelligence property issue. It gives intel( even if not big) on how the app is built. Plus it’s no use when packaged 😉