I am trying to setup a Polymer Blank application w these instructions
https://www.polymer-project.org/2.0/start/install-2-0
I am using the latest ver of node, npm and polymer
I create a test project (redcloud) and use polymer init w app template
polymer server shows blank screen
running polymer build and also js compile option both return the error below...
sudo polymer build --js-compile
info: Clearing build/ directory...
info: (default) Building...
error: Uncaught exception: Error: ENOENT: no such file or directory,
open '/Users/greg/redcloud/bower_components/webcomponentsjs/webcomponents-loader.js'
error: Error: ENOENT: no such file or directory, open '/Users/greg/redcloud/bower_components/webcomponentsjs/webcomponents-loader.js'
Run bower install before trying to build the app. (It seems there are some missing bower dependencies.)
Related
This is my repository https://github.com/Shrinivassab/Portfolio
I am trying to create a portfolio website. When I try to run vercel build
I am getting the below error
Traced Next.js server files in: 1.490s
Created all serverless functions in: 788.915ms
Collected static files (public/, static/, .next/static): 4.085ms
Error: EPERM: operation not permitted, symlink 'getExperience.func' -> 'D:\Coding Examples\portfolio\.vercel\output\functions\api\getPageInfo.func'
Do any suggestions please? Thanks in advance
Run yarn dev(or npm run dev) in your project file
Then run the terminal as administrator and cd your project folder then run vercel build command
After then, delete the folder inside .vercel\output\functions\_next\data
and deploy vercel deploy --prebuilt
I could get help from some youtube comments. and it works for me
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.
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'
We are migrating CSS-loader from v0.28.11 to v3.1.0
We have 2 projects:
Project A- No component dependency on any other project - (containing some components)
Project B - We are importing Project A as node modules
We are able to run and build project A successfully.
But when we try to run Project B we getting a dependancy error for css files from Project A.
ERROR in ./src/help/css/about.qcss
Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
ModuleNotFoundError: Module not found: Error: Can't resolve './Project/A/src/typography/css/qx-typography.css' in 'D:\Projects\B\src\help\css'
at factory.create (D:\Projects\B\node_modules\webpack\lib\Compilation.js:823:10)
at factory (D:\Projects\B\node_modules\webpack\lib\NormalModuleFactory.js:397:22)
at resolver (D:\Projects\B\node_modules\webpack\lib\NormalModuleFactory.js:130:21)
at asyncLib.parallel (D:\Projects\B\node_modules\webpack\lib\NormalModuleFactory.js:224:22)
at D:\Projects\B\node_modules\neo-async\async.js:2830:7
at D:\Projects\B\node_modules\neo-async\async.js:6877:13
at normalResolver.resolve (D:\Projects\B\node_modules\webpack\lib\NormalModuleFactory.js:214:25)
at doResolve (D:\Projects\B\node_modules\enhanced-resolve\lib\Resolver.js:184:12)
at hook.callAsync (D:\Projects\rx\node_modules\enhanced-resolve\lib\Resolver.js:238:5)
at _fn0 (eval at create (D:\Projects\B\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:15:1)
Same works fine with if we do css-loader of Project A to v3.1.0 and Project B to v1.0.0
But we get a compile-time error if we change both project css-loader version to 3.1.0
We should be able to run and create a build using CSS-loader with version 3.1.0
Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
ModuleBuildError: Module build failed (from ./node_modules/sass-loader/dist/cj s.js):
Error: Missing binding /home/user/frontloja/node_modul es/node-sass/vendor/ linux-x64-64/binding.node
Node Sass could not find a binding for your current environment : Linux 64-bit with Node.js 10.x
Found bindings for the following environments:
- Linux 64-bit with Node.js 12.x
In my case, it happened after I updated ubuntu 18 to 20, so I did it like this
remove or rename node_modules
then reinstall use npm or yarn install
This issue happens because of webpack resolve.alias not works
To solve this issue we can use the relative path.
In my case
Currently, I am in Projects\B\src\help\css
and requiring file from node_Modules
/Project/A/src/typography/css/qx-typography.css
so my path be like (**Relative Path**)
../../../../node_modules/Project/A/src/typography/css/qx-typography.css";
Error: ./src/styles.css
Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
ModuleBuildError: Module build failed (from ./node_modules/postcss-loader/dist/cjs.js):
Error: Failed to find 'bootstrap/dist/css/bootstrap.min.css'
Solution:
Run the following command for installing additional packages
npm install bootstrap jquery popper.js
I had this issue in my Angular project. It looks like a bootstrap issue. I just downgraded bootstrap from 5.1.3 to 4.6.0. That's all
I was following up a tutorial which used expo and needed the fonts for native code, but I'm not using expo thus I don't need those fonts. I removed the code that was using them (nothing that would affect the other parts of the app), and now it gives me this hideous error that it says is located on my source folder "src/navigation/node_modules/native-base/Fonts", the node modules are not even located on the src.
Bear in mind that I'm new to react native, any help would be appreciated.
Terminal output:
bundling failed: Error: ENOENT: no such file or directory, scandir
'/Users/relativity/Documents/ReactNative-Projects/test/src/navigation/node_modules/native-base/Fonts'
Try npm install in your project directory, perhaps you deleted something that wasn't meant to be deleted.
Open terminal and navigate to your project directory and run npm install after it is done run react-native run-android or react-native run-ios
It looks like some default fonts are missing.
npm rebuild native-base is the official solution. Deleting your node_modules and running npm install will also do the trick. If this doesn't work try clearing cache, deleting node_modules and installing packages.