You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I agree to follow the code of conduct that this project uses.
I have searched the issue tracker for a bug that matches the one I want to file, without success.
Electron Forge version
6.2.1
Electron version
25.3.1
Operating system
Windows 10
Last known working Electron Forge version
6.2.1
Expected behavior
packagerConfig.ignore All paths should be processed
Actual behavior
I want to optimize the volume of packaged files and preserve specific files through the ignore function, but I found that the ignore function does not handle all paths
Please take a look at the ignore section in my code. This logic is very simple, but/node_ Modules/electric squirrel startup, some of which were not matched
I faced a similar situation and solved it as follows:
ignore(path){if(!path)returnfalse;if(path.startsWith("/package.json"))returnfalse;// add only the /.vite folder from the project root, ignoring the one in node_modules.if(path.startsWith("/.vite"))returnfalse;// allow the node_modules folder, if we do not do this, we will not have access to the electron-squirrel-startup folder.if(path==="/node_modules")returnfalse;if(path.startsWith("/node_modules/electron-squirrel-startup"))returnfalse;returntrue;}
Pre-flight checklist
Electron Forge version
6.2.1
Electron version
25.3.1
Operating system
Windows 10
Last known working Electron Forge version
6.2.1
Expected behavior
packagerConfig.ignore All paths should be processed
Actual behavior
I want to optimize the volume of packaged files and preserve specific files through the ignore function, but I found that the ignore function does not handle all paths
Please take a look at the ignore section in my code. This logic is very simple, but/node_ Modules/electric squirrel startup, some of which were not matched
Steps to reproduce
Additional information
No response
The text was updated successfully, but these errors were encountered: