I'm getting this error now after deleting node_modules and doing a fresh npm install
$ ng build
Your global Angular CLI version (14.1.0-next.0) is greater than your local version (13.3.7). The local Angular CLI version is used.
To disable this warning use "ng config -g cli.warnings.versionMismatch false".
- Generating browser application bundles (phase: setup)...
Another process, with id 2112, is currently running ngcc.
Waiting up to 250s for it to finish.
(If you are sure no ngcc process is running then you should delete the lock-file at C:/ClientApp/node_modules/.ngcc_lock_file.)
√ Browser application bundle generation complete.
√ Browser application bundle generation complete.
./node_modules/angular2-signaturepad/fesm2015/angular2-signaturepad.mjs:3:0-52 - Error: Module not found: Error: Can't resolve 'signature_pad' in 'C:\ClientApp\node_modules\angular2-signaturepad\fesm2015'
I'm at a loss. I'm using Angular 13.3.0 and this was working great.
I need to get this fixed. I have scoured the internet for this problem but even though the file is there in node_modules, it can't find it.
Related
I'm trying to make alarm clock with Expo.
I am using the react-native-simple-alarm library. It asks for the deprecated #react-native-community/async-storage.
How can this be made to work?
ERROR Error: [#RNC/AsyncStorage]: NativeModule: AsyncStorage is null.
To fix this issue try these steps:
• Run react-native link #react-native-community/async-storage in the project root.
• Rebuild and restart the app.
• Run the packager with --reset-cache flag.
• If you are using CocoaPods on iOS, run pod install in the ios directory and then rebuild and re-run the app.
• If this happens while testing with Jest, check out docs how to integrate AsyncStorage with it: https://react-native-community.github.io/async-storage/docs/advanced/jest
If none of these fix the issue, please open an issue on the Github repository: https://github.com/react-native-community/react-native-async-storage/issues
ERROR Invariant Violation: "main" has not been registered. This can happen if:
Metro (the local dev server) is run from the wrong folder. Check if Metro is running, stop it and restart it in the current project.
A module failed to load due to an error and AppRegistry.registerComponent wasn't called.
We have issue found during installing a new expo app whenever we update newer version of expo app from play store our development related things not working so we have updated it with expo sdk 45 but it giving error still so we have set a new environment and trying to solve this after set new environment it still giving errors like below
ERROR Error: Requiring module "node_modules\react-native-reanimated\src\Animated.js", which threw an exception: Error: Reanimated 2 failed to create a worklet, maybe you forgot to add Reanimated's babel plugin?
ERROR Invariant Violation: "main" has not been registered. This can happen if:
Metro (the local dev server) is run from the wrong folder. Check if Metro is running, stop it and restart it in the current project.
A module failed to load due to an error and AppRegistry.registerComponent wasn't called.
I don't think this is a fix for everyone, but try:
yarn global add expo-cli
(Mine upgraded when I do this)
yarn install
(To rebuild the package)
expo --version
Then use the package version on the package.json
"expo-cli": "5.4.12",
expo start
Give it a go, you might be lucky...
I'm using yarn 3.2.0(latest) and node 17.6.0(latest)
As instructed in CRA documentation I ran yarn create react-app myapp. It completed installation and was able to start the app using yarn start. However after making changes to the App , I always get the following error
ERROR
Failed to load config "react-app" to extend from.
Referenced from: D:\myapp\package.json
If I install any packages, I get module not found error like below
ERROR in ./src/App.js 6:0-39
Module not found: Error: Can't resolve 'styled-components' in 'D:\myapp\src'
Anyone know what's going on?
I had a similar issue. And found that the reason why this was happening to me was due to my Antivirus. Try disabling your antivirus on windows if you have one and re-create your project and if that fixes your issue.
I am trying to compile my first React Native project, and it all works fine from the CLI, until I try to install a new library.
After installing any library, I get various errors, culminating in this:
error: bundling failed: Error: While trying to resolve module `react` from file `/Users/myname/Desktop/Projects/ProjectName/App.js`, the package `/Users/myname/Desktop/Projects/ProjectName/node_modules/react/package.json` was successfully found. However, this package itself specifies a `main` module field that could not be resolved (`/Users/myname/Desktop/Projects/ProjectName/node_modules/react/index.js`. Indeed, none of these files exist:
I have, indeed, confirmed that those files exist.
What is going on here? I'm constantly having these errors as I am trying to use React Native, even when rebuilding the app multiple times and trying over.
Do the following steps:
Stop metro bundler
Delete node_modules folder
cd into your project folder and run:
'npm install'
I am using angular 1.4.14, bower 1.8.0 and npm 3.6.0. I have used the following yeoman generator,https://github.com/dustinspecker/generator-ng-poly, to setup my project. I have full fledged web-ui ready in development mode when i run "gulp" cmd. But when i'm trying to generate production build by 'gulp --stage prod', which terminates without any log before minifying the templates. Find below the last logs generated,
[22:29:06] ESLint found no problems in 1 file
[22:29:06] Finished 'markup' after 2.29 s
[22:29:06] Starting 'scripts'...
[22:29:13] gulp-imagemin: Minified 26 images (saved 109.57 kB - 12.9%)
[22:29:13] Finished 'scripts' after 6.69 s
[22:29:13] Finished 'images' after 8.73 s
user#user:frontend$
I have checked all the console logs prior to this, there isn't any error or fatal error message displayed. The same code works in development mode.
How do I know whats failing the production build?