-
-
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
Installing and initializing the live-plugin-manager breaks the module build #1929
Comments
I get the same issue when updating @electron-forge above version 6.0.0-beta.50. Tested with 6.0.0-beta.52, 6.0.0-beta.53, 6.0.0-beta.54 |
similar issue: #1726 |
Many thanks, I tries to downgrade @electron_forge to version 6.0.0-beta.50 but this did not help
|
Sorry to hear. Seems that webpack combined with native modules is a hard nut to crack: #621 (comment) |
Import This is caused by module.exports = [
// Add support for native node modules
{
test: /\.node$/,
use: 'node-loader',
},
// {
// test: /\.(m?js|node)$/,
// parser: { amd: true },
// use: {
// loader: '@zeit/webpack-asset-relocator-loader',
// options: {
// outputAssetBase: 'native_modules',
// emitDirnameAll: true,
// },
// },
// },
{
test: /\.tsx?$/,
... I can't understand why we need this plugin, it seems useless according to its readme... And I try replace it with So currently just comment it out, and it is fixed. |
Many thanks @linonetwo, I commented the rule out and this fixed the build errors. I also wonder what the |
|
well, why electron-forge works fine without it? |
Unless you're using a native node module, you are unlikely to need |
I don't know but in my project if I use the original @vercel/webpack-asset-relocator-loader work fine also with native modules. |
Still getting this with v6.0.0-beta.59. Hoping for #2149 to solve it 🙏 |
v6.0.0-beta.60 finally solved this for us 🚀 |
Nope, on next
Weird that that did not happen on the first run of |
So this issue should be re-opened |
No, see https://www.electronforge.io/config/plugins/webpack#native-modules |
O.k., so after lots of experimenting I completely changed the way to use externals. I am now following https://www.electronforge.io/config/plugins/webpack#native-modules closely, using What broke it for me was the fact that my project had quite some history, struggling with the native library. So it used a lot of tips and tricks found in a number of other issues. Which seem not to work anymore for newer versions of electron-forge. Add to that my not understanding what is going on here, and you get quite a confusing mess. Thanks a lot for this great tool, @malept |
Preflight Checklist
Issue Details
Expected Behavior
I followed the instructions at live-plugin-manager
Actual Behavior
After installing the
live-plugin-manager
and initializing the manager as:the
npm start
results in App throwing following error:To Reproduce
Pull the electron-app branch of my app, install the
live-plugin-manager
and initialize the manager.Additional Information
Generally this bug might be caused by the
live-plugin-manager
. I am seraching for solution allowing users locally install npm packages without needing to depend on npm installation. I tried to fetch those packages via HTTP, but then their dependencies are not installed. Maybe there is another way of achieving this without needing to use thelive-plugin-manager
Full log with DEBUG=*
https://pastebin.com/zkBdNQfr
The text was updated successfully, but these errors were encountered: