-
Notifications
You must be signed in to change notification settings - Fork 110
Known local error messages with solutions
This is a non-extensive list of issues that more people have encountered when running the solution locally
Please add your error messages to this list, if you think they are common.
When trying to run the frontend you get the message:
index.js:6:26: Cannot resolve dependency '@ifrc-cbs/common-react-ui'
Solution:
- Go to Source/Navigation/Web.Commons do "npm install"
- Go to Source/Navigation/Web.Nodejs do "npm install"
- Go to Source/..bounded context../Web do "npm install"
When trying to run the frontend you get the message
(node:17884) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Cannot find module './lib/fs'
Solution: Update your version of node to version 8 or newer.
Ref: https://github.com/parcel-bundler/parcel/issues/2533
Npm install doesn't work. If you are on Windows some bounded contexts demands that you run npm install in a console that supports cp.
Solution: Switch to ie. Git Bash and try to run the command again
[parcel:dev ] × C:\....\Source\Alerts\Web\node_modules\@dolittle\queries\dist\esmodule\Query.js:10:16: This experimental syntax requires enabling the parser plugin: 'classProperties' (10:16)
Solution: There is an issue in Dolittle. Until doLittle has fixed an issue be aware that all references in frontend to their queries and commands needs to be fixed manually. This affects the files in Web/Features
When they generate proxies, in the top of their files they import @dolittle/commands and @dolittle/queries depending on the domain model. To fix it change them to @dolittle/commands/dist/commonjs and @dolittle/queries/dist/commonjs. Afterwards you will probably have to restart your frontend with "npm start". (edited)