-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error #9417
Comments
I got the issue resolved by replacing loaders keyword with rules. |
try removing "!" in the folder name.. i usually do the same - put "!' so that it would be sorted to the top, in this case webpack has reservation for that symbol ... |
The same happened to me. Apparently the error is caused when some directory in the project path has the symbol "!" in its name. Removing the symbol solves the problem. In your case, the !BisnesHelper directory is the cause of the problem |
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs. |
I don't think there's much we can do about this one. Just avoid directory names that start with |
I write create-react-app myapp, after all installations I write npm start, and an error appears. Why?
{Failed to compile.
Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! bisness@0.1.0 start:
react-scripts start
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the bisness@0.1.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Lenovo\AppData\Roaming\npm-cache_logs\2020-08-04T11_10_57_995Z-debug.log
PS D:!BisnesHelper\bisness> npm start
Failed to compile.
Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! bisness@0.1.0 start:
react-scripts start
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the bisness@0.1.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Lenovo\AppData\Roaming\npm-cache_logs\2020-08-04T11_15_23_920Z-debug.log}
The text was updated successfully, but these errors were encountered: