-
Notifications
You must be signed in to change notification settings - Fork 213
Massive error message in development when unable to resolve a file #875
Comments
Hi! Thank you for filing this issue -- I get these verbose error messages in my projects and they annoy me too! (I should have looked into this sooner haha) Digging around I found webpack/webpack#818, which said that the error message is only shown when We don't set that pref for ...however the linked webpack issue above says that The issue is made worse by the fact that Neutrino defaults to having a long list of file extensions (we should probably make In the meantime a workaround for the module.exports = {
use: [
[
'@neutrinojs/react',
{
devServer: {
stats: {
errorDetails: false,
},
},
},
],
]
}; Thankfully the build case will be fixed by #852 (which will be in Neutrino 9) - since it switches to using the native webpack CLI tools - so doesn't hand-roll the errors analysis. However we'll still need to fix the devserver's stats to stop setting @eliperelman, do you think we can backport |
@edmorley I'm OK with that, I'd count it more as a bug than a breaking change. |
v8.3.0 has just been released, which includes the fix for devServer (builds will be fixed in Neutrino 9). |
Bug or issue?
Please try to answer the following questions:
neutrino start
when there is an unresolved module in a fileOccasionally I accidentally import something from the wrong file after some refactoring. Happens. When I run
neutrino start
, I would expect it to tell me that a certain thing can't be found, but I get a HUGE error message which tells me essentially the same thing. It's slightly amusing but can be annoying at times. I find this typically only happens when imports cannot be found. Example:And the big one:
My
.neutrinorc.js
is pretty standard:const BundleAnalyzerPlugin = require('webpack-bundle-analyzer').BundleAnalyzerPlugin;
const webpack = require('webpack');
Seems related to this actually: https://stackoverflow.com/questions/43037590/field-browser-doesnt-contain-a-valid-alias-configuration?utm_medium=organic&utm_source=google_rich_qa&utm_campaign=google_rich_qa
Feature request or enhancement?
Please describe your request in detail. Use the following questions as guidance:
The text was updated successfully, but these errors were encountered: