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 follows, as appropriate.
I have searched the issue tracker for an issue that matches the one I want to file, without success.
Please describe your issue:
When using no linked dependency, everything works flawlessly. When using a linked dependency (after running yarn link {insert package} I get the following error:
Uncaught Error: Couldn't find preset "env" relative to directory "D:\\Code\\ipfs-shipyard\\ipfs-react-components\\dist"
at D:\Code\ipfs-shipyard\ipfs-desktop\node_modules\babel-core\lib\transformation\file\options\option-manager.js:293:19
at Array.map (native)
at OptionManager.resolvePresets (D:\Code\ipfs-shipyard\ipfs-desktop\node_modules\babel-core\lib\transformation\file\options\option-manager.js:275:20)
at OptionManager.mergePresets (D:\Code\ipfs-shipyard\ipfs-desktop\node_modules\babel-core\lib\transformation\file\options\option-manager.js:264:10)
at OptionManager.mergeOptions (D:\Code\ipfs-shipyard\ipfs-desktop\node_modules\babel-core\lib\transformation\file\options\option-manager.js:249:14)
at OptionManager.init (D:\Code\ipfs-shipyard\ipfs-desktop\node_modules\babel-core\lib\transformation\file\options\option-manager.js:368:12)
at File.initOptions (D:\Code\ipfs-shipyard\ipfs-desktop\node_modules\babel-core\lib\transformation\file\index.js:212:65)
at new File (D:\Code\ipfs-shipyard\ipfs-desktop\node_modules\babel-core\lib\transformation\file\index.js:135:24)
at Pipeline.transform (D:\Code\ipfs-shipyard\ipfs-desktop\node_modules\babel-core\lib\transformation\pipeline.js:46:16)
at BabelCompiler.compileSync (D:\Code\ipfs-shipyard\ipfs-desktop\node_modules\electron-compilers\lib\js\babel.js:81:26)
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.
PS D:\Code\ipfs-shipyard\ipfs-desktop> yarn start
yarn run v1.3.2
$ electron-forge start
WARNING: DEBUG environment variable detected. Progress indicators will be sent over electron-forge:lifecycle
electron-forge:lifecycle Process Started: Checking your system +0ms
electron-forge:lifecycle Process Succeeded: Checking your system +936ms
electron-forge:runtime-config setting key: verbose to value: false +0ms
WARNING: DEBUG environment variable detected. Progress indicators will be sent over electron-forge:lifecycle
electron-forge:lifecycle Process Started: Locating Application +0ms
electron-forge:project-resolver searching for project in: D:\Code\ipfs-shipyard\ipfs-desktop +0ms
electron-forge:project-resolver electron-forge compatible package.json found in D:\Code\ipfs-shipyard\ipfs-desktop\package.json +9ms
electron-forge:lifecycle Process Succeeded: Locating Application +15ms
electron-forge:lifecycle Process Started: Preparing native dependencies +11ms
electron-forge:lifecycle Process Succeeded: Preparing native dependencies +1s
electron-forge:hook could not find hook: generateAssets +0ms
electron-forge:lifecycle Process Started: Launching Application +9ms
electron-forge:lifecycle Process Succeeded: Launching Application +7ms
What command line arguments are you passing?
None.
What does your config.forge data in package.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 the
source of your problem.
git clone https://github.com/ipfs-shipyard/ipfs-desktop
git clone https://github.com/ipfs-shipyard/ipfs-react-components
cd ipfs-react-components && yarn && yarn link && cd ..
cd ipfs-desktop && yarn && yarn link ipfs-react-components && yarn start
It happens with other linked dependencies too. This is making the development very slow since I always have to deploy the dependency and then update the electron app...
The text was updated successfully, but these errors were encountered:
As of electron-forge@6.0.0 we don't use electron-compile by default. If you still experience this issue in a post-6.0.0 world you should raise an issue on electron-compile.
Please describe your issue:
When using no linked dependency, everything works flawlessly. When using a linked dependency (after running
yarn link {insert package}
I get the following error: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?
None.
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.
It happens with other linked dependencies too. This is making the development very slow since I always have to deploy the dependency and then update the electron app...
The text was updated successfully, but these errors were encountered: