Closed torifat closed 7 years ago
This should now be fixed in neutrino@v4.2.1. Thanks!
Sadly it's not fixed yet for me 😢
@torifat could you maybe share an updated package.json? I tested this change to package.json locally and it worked for me. To confirm, I added a file called override.js
, added it my presets, and put the following code in it to ensure the value was loaded:
package.json
"scripts": {
"start": "neutrino start"
},
"dependencies": {
"neutrino": "^4.2.1",
"neutrino-preset-react": "^4.2.0",
"react": "^15.4.2",
"react-dom": "^15.4.2"
},
"config": {
"presets": [
"neutrino-preset-react",
"override.js"
],
"neutrino": {
"module": {
"rule": {
"css": {
"loader": {
"css": {
"options": {
"modules": true
}
}
}
}
}
}
}
}
override.js
module.exports = neutrino => {
neutrino.on('prestart', () => {
console.log(neutrino.config.module.rule('css').loaders.get('css').options);
process.exit(0);
});
};
console
❯ yarn start
yarn start v0.20.3
$ neutrino start
{ modules: true }
✨ Done in 1.13s.
Here's the stack-trace: