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'm using yarn workspaces which links workspace packages under node_modules without running babel on the package. For this reason I'd like to ensure that my razzle setup runs babel on these packages.
Most likely my problem can be simplified to "run babel also for imports under node_modules/@myorg", potentially with the complication that these packages are symlinks.
I've tried changing my configuration by adding a razzle.config.js webpack override, which runs during packaging
constpath=require('path');module.exports={modify: (config,{ target, dev },webpack)=>{// rules[2] is the babel loader.config.module.rules[2].include.push(path.join(__dirname,'./node_modules/@myorg'));returnconfig;},}
Everything seems to be going fine when I run the build script. My code comes out transpiled correctly. However, when I'm running the start scripts, I keep getting an error preventing the server from starting.
Any advice?
The text was updated successfully, but these errors were encountered:
I'm using yarn workspaces which links workspace packages under node_modules without running babel on the package. For this reason I'd like to ensure that my razzle setup runs babel on these packages.
Most likely my problem can be simplified to "run babel also for imports under node_modules/@myorg", potentially with the complication that these packages are symlinks.
I've tried changing my configuration by adding a razzle.config.js webpack override, which runs during packaging
constpath=require('path');module.exports={modify: (config,{ target, dev },webpack)=>{// rules[2] is the babel loader.config.module.rules[2].include.push(path.join(__dirname,'./node_modules/@myorg'));returnconfig;},}
Everything seems to be going fine when I run the build script. My code comes out transpiled correctly. However, when I'm running the start scripts, I keep getting an error preventing the server from starting.
I'm using yarn workspaces which links workspace packages under
node_modules
without running babel on the package. For this reason I'd like to ensure that my razzle setup runs babel on these packages.Most likely my problem can be simplified to "run babel also for imports under
node_modules/@myorg
", potentially with the complication that these packages are symlinks.I've tried changing my configuration by adding a
razzle.config.js
webpack override, which runs during packagingEverything seems to be going fine when I run the
build
script. My code comes out transpiled correctly. However, when I'm running thestart
scripts, I keep getting an error preventing the server from starting.Any advice?
The text was updated successfully, but these errors were encountered: