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
While using big libraries the electron forge fails to compile them.
Step 1:
electron-forge start
Console output when you run electron-forge with the environment variable DEBUG=electron-forge:*. (Instructions on how to do so here). Please include the stack trace if one exists.
⠹ Checking your system⚠ You are using NPM, but not a known good version. The known versions that work with Electron Forge are: ^3.0.0 || ^4.0.0 || ~5.1.0 || ~5.2.0 || >= 5.4.0
✔ Checking your system
✔ Locating Application
✔ Preparing native dependencies
✔ Launching Application
Warning, the following targets are using a decimal version:
electron: 1.7
We recommend using a string for minor/patch versions to avoid numbers like 6.10
getting parsed as 6.1, which can lead to unexpected behavior.
This platform is ${process.platform}
Warning, the following targets are using a decimal version:
electron: 1.7
We recommend using a string for minor/patch versions to avoid numbers like 6.10
getting parsed as 6.1, which can lead to unexpected behavior.
Warning, the following targets are using a decimal version:
electron: 1.7
We recommend using a string for minor/patch versions to avoid numbers like 6.10
getting parsed as 6.1, which can lead to unexpected behavior.
Warning, the following targets are using a decimal version:
electron: 1.7
We recommend using a string for minor/patch versions to avoid numbers like 6.10
getting parsed as 6.1, which can lead to unexpected behavior.
Warning, the following targets are using a decimal version:
electron: 1.7
We recommend using a string for minor/patch versions to avoid numbers like 6.10
getting parsed as 6.1, which can lead to unexpected behavior.
Warning, the following targets are using a decimal version:
electron: 1.7
We recommend using a string for minor/patch versions to avoid numbers like 6.10
getting parsed as 6.1, which can lead to unexpected behavior.
Warning, the following targets are using a decimal version:
electron: 1.7
We recommend using a string for minor/patch versions to avoid numbers like 6.10
getting parsed as 6.1, which can lead to unexpected behavior.
Warning, the following targets are using a decimal version:
electron: 1.7
We recommend using a string for minor/patch versions to avoid numbers like 6.10
getting parsed as 6.1, which can lead to unexpected behavior.
Warning, the following targets are using a decimal version:
electron: 1.7
We recommend using a string for minor/patch versions to avoid numbers like 6.10
getting parsed as 6.1, which can lead to unexpected behavior.
Warning, the following targets are using a decimal version:
electron: 1.7
We recommend using a string for minor/patch versions to avoid numbers like 6.10
getting parsed as 6.1, which can lead to unexpected behavior.
Warning, the following targets are using a decimal version:
electron: 1.7
We recommend using a string for minor/patch versions to avoid numbers like 6.10
getting parsed as 6.1, which can lead to unexpected behavior.
Warning, the following targets are using a decimal version:
electron: 1.7
We recommend using a string for minor/patch versions to avoid numbers like 6.10
getting parsed as 6.1, which can lead to unexpected behavior.
Warning, the following targets are using a decimal version:
electron: 1.7
We recommend using a string for minor/patch versions to avoid numbers like 6.10
getting parsed as 6.1, which can lead to unexpected behavior.
[BABEL] Note: The code generator has deoptimised the styling of "/Users/ruvenss/uielectronforge/js/widgets/jqx-all.js" as it exceeds the max of "500KB".
What command line arguments are you passing?
start
What does your config.forge data in package.json look like?
Note how the message is prepended with [BABEL]. That means that the code that has the limit is Babel, not Electron Forge itself. If you search for 500KB in the Babel repository, you'll see why. It doesn't appear to be a configurable value, so we can't do much about that.
electron: 1.7
While using big libraries the electron forge fails to compile them.
Step 1:
electron-forge start
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.What command line arguments are you passing?
What does your
config.forge
data inpackage.json
look like?I am including the library jqxwidgets in my project which uses heavy files
The text was updated successfully, but these errors were encountered: