when I am running gulp serve for my angularjs fuse project. this error will be shown.
C:\wamp\www\bank_admin_post_login\Fuse-1.4.1-demo>gulp serve
C:\wamp\www\bank_admin_post_login\Fuse-1.4.1-demo>npm rebuild node-sass
I am running above commands.
Try install an ancient version of Node JS, I suggest you 4.2.2
Related
I'm trying to build a cloned project, but I'm getting an error:
The command 'gulp build' exited with code 1".
First of all I had another error:
The command 'build build' exited with code 9009
I realized that I need a gulp node module and installed it.
But after that, it's also exited with code 1.
I think that the problem is in NuGet Packages maybe, but I'm not sure.
You need to install bower
npm install bower -g
Please find the stack over here...
Installing packages...npm WARN deprecated tslint#6.1.2: TSLint has been deprecated in favor of ESLint. Please see https://github.com/palantir/tslint/issues/4534 for more information.
npm WARN deprecated request#2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated chokidar#2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated fsevents#1.2.12: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated urix#0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated resolve-url#0.2.1: https://github.com/lydell/resolve-url#deprecated
npm ERR! Unexpected end of JSON input while parsing near '...iERRHPyU8nBqZB1+iv2Uh'
I had the exact same error and was able to fix it through following steps.
Run npm cache clean --force
Manually delete npm and npm-cache folders from AppData/Roaming folder (Win + R, Type %AppData% and enter)
Run Node Installer and repair
Reinstall npm install -g #angular/cli
Rerun ng new newApp
Worked :)
Use node V12.4.0 and npm V6.9.0
i was getting the same issue please try reinstall angular CLI after installing previous one
I think this can only be achieved if we first update the version to 8 and then move from 8 to 9.
I had the same Issue and Following steps worked for me.
Delete npm-cache in AppData/Roaming
Reinstall the angular cli by 'npm install -g #angular/cli'
Then Create the project
Run npm cache clean --force
Manually delete npm and npm-cache folders from AppData/Roaming folder (Win + R, Type %AppData% and enter)
Run Node Installer and repair
4.Reinstall npm install -g #angular/cli
Rerun ng new newApp
Worked :)
https://github.com/npm/cli/issues/1191
Delete the AppData\Roaming\npm-cache folder and then try creating the project again. This is really gonna work =)
I am trying to initialize a Hexo site on my Windows 10 PC. I have Node 9.9.0 installed as well as git 2.16.2.windows.1.
I have run npm install hexo-cli -g and it installs fine. I then go about the steps listed to create and initialize a site (hexo init test-site) and get the following errors.
I've tried a fresh install of node and git, running npm install a-sync-waterfall -g, and adding a file to node_modules called .a-sync-waterfall.DELETE; but hexo init still fails. Manually running npm install also gives me the same error.
Any ideas? Thanks.
Windows and NPM are not the most stable together. I've found Yarn to much more stable.
Try one of these two things:
Use Yarn
Delete node_modules folder, clear the NPM global cache, attempt a hexo init
del node_modules
npm cache clear --force
hexo init test-site
after setting up semantic folder in my project folder i get an error when i use 'gulp build' command:
aayush#aayushs-computer:~/Desktop/NewP$ sudo npm install semantic-ui
[sudo] password for aayush:
npm WARN deprecated gulp-clean-css#2.4.0: breaking changes from clean-css 4.x. Please install gulp-clean-css 3.x
npm WARN deprecated minimatch#2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch#0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated graceful-fs#1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs#^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN prefer global js-beautify#1.5.10 should be installed with -g
npm WARN prefer global marked#0.3.6 should be installed with -g
> semantic-ui#2.2.10 install /home/aayush/Desktop/NewP/node_modules/semantic-ui
> gulp install
[20:19:41] Using gulpfile ~/Desktop/NewP/node_modules/semantic-ui/gulpfile.js
[20:19:41] Starting 'install'...
[20:19:41] Starting 'run setup'...
? Set-up Semantic UI Express (Set components and output folder)
?
We detected you are using NPM. Nice!
Is this your project folder?
/home/aayush/Desktop/NewP
Yes
? Where should we put Semantic UI inside your project? semantic/
? What components should we include in the package? reset, site, button, contain? Should we set permissions on outputted files? No
? Do you use a RTL (Right-To-Left) language? No
? Where should we output Semantic UI? out
[20:20:46] Finished 'run setup' after 1.08 min
[20:20:46] Starting 'create install files'...
Installing
------------------------------
Installing to semantic/
Copying UI definitions
Copying UI themes
Copying gulp tasks
Adding theme files
Creating gulpfile.js
Creating site theme folder /home/aayush/Desktop/NewP/semantic/src/site/
[20:20:46] Starting 'create theme.config'...
Adjusting #siteFolder to: site/
Creating src/theme.config (LESS config) /home/aayush/Desktop/NewP/semantic/src/theme.config
[20:20:46] Finished 'create theme.config' after 21 ms
[20:20:46] Starting 'create semantic.json'...
Creating config file (semantic.json) /home/aayush/Desktop/NewP/semantic.json
[20:20:46] Finished 'create semantic.json' after 20 ms
[20:20:46] Finished 'create install files' after 177 ms
[20:20:46] Starting 'clean up install'...
Setup Complete!
Installing Peer Dependencies. Please refrain from ctrl + c...
After completion navigate to semantic/ and run "gulp build" to build
> fsevents#1.1.2 install /home/aayush/Desktop/NewP/node_modules/fsevents
> node install
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN newp#1.0.0 No repository field.
+ semantic-ui#2.2.10
added 681 packages in 133.426s
aayush#aayushs-computer:~/Desktop/NewP$ cd sematic/
bash: cd: sematic/: No such file or directory
aayush#aayushs-computer:~/Desktop/NewP$ cd semantic/
aayush#aayushs-computer:~/Desktop/NewP/semantic$ gulp build
No command 'gulp' found, did you mean:
Command 'gslp' from package 'ghostscript' (main)
gulp: command not found
i have read and tried all things in https://github.com/Semantic-Org/Semantic-UI/issues/2086. problem still there.
Here are the exact steps I took to try to run the hello.js example for spooky js on nitrous.
1. I installed phantomjs, nodejs(already installed), and casperjs.
$ npm install -g casperjs
Casper warns me that While CasperJS is installable via npm, it’s not a NodeJS package, neither it’s capable to require native NodeJS modules.
Because of this I wanted to use spookyjs which is a nodejs package.
Then, I installed phantom js: $ npm install phantomjs
Finally, I installed spookyjs: $ npm install spooky
2. I tried running the hello.js example using
$ node node_modules/spooky/examples/hello.js
3. I end up getting this error:
{ [Error: Child terminated with non-zero exit code 1] details: { code: 1, signal: null }}
Am I doing something wrong or can casperjs not be installed?
this is where I found spookyjs
Have you installed the phantomjs and casperjs runtime? The npm packages for phantomjs and casperjs call out to these runtimes. The error you see is when it can not find the casperjs runtime.
I'm not very familiar with nitrous.io and how much freedom you have to install other runtimes. Here's what I used for installing them on Linux: https://www.dvdheiden.nl/2013/07/30/installing-phantomjs-and-casperjs-on-linux/