-
-
Notifications
You must be signed in to change notification settings - Fork 523
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Webpack template: index.css file missing when packaged #1030
Comments
I tried to solve this by downgrading:
|
|
The issue still exists in beta 41 (as described on #1032): {
"@electron-forge/cli": "6.0.0-beta.41",
"@electron-forge/maker-deb": "6.0.0-beta.41",
"@electron-forge/maker-rpm": "6.0.0-beta.41",
"@electron-forge/maker-squirrel": "6.0.0-beta.41",
"@electron-forge/maker-zip": "6.0.0-beta.41",
"@electron-forge/plugin-webpack": "6.0.0-beta.41",
} Also, downgrading to beta 39 did not solve the issue, where the same happens. The dependencies are the following:
|
Beta 39 had the index.js issue but not the CSS file issue (as there was no CSS file). Please be patient, I'm trying to release a new version as fast as possible. |
No worries, I just wanted to register that. I've already made a rewrite on my app so it can build without Webpack. |
This has been fixed in beta 42. |
@malept, thank you for your work, I really did not expect this to be looked at so quickly. I tried my initial approach this morning again with beta 42, but I'm still having the same trouble with This is the reproduction steps:
|
Hi all, Same problem here with index.js getting 404 Version: 6.0.0-beta.42 |
The |
I updated to @electron-forge/plugin-webpack-6.0.0-beta.41 and build does not work anymore. It is reproducible just by trying this out on the webpack template. Steps to reproduce below. Everything runs without errors or warnings.
Console output when you run
electron-forge
with the environment variableDEBUG=electron-forge:*
. (Instructions on how to do so here). Please include the stack trace if one exists.This is the package output:
What does your
config.forge
data inpackage.json
look like?Please provide either a failing minimal testcase (with a link to the code) or detailed steps to
reproduce your problem. Using
electron-forge init
is a good starting point, if that is not thesource of your problem.
The text was updated successfully, but these errors were encountered: