I followed Microsoft docs for setting the SharePoint framework. https://learn.microsoft.com/en-us/sharepoint/dev/spfx/set-up-your-development-environment But when I got to the point where you are supposed to install the generator it gives me this error.
>>
PS C:\Users\jakub.yaghob> npm install #microsoft/generator-sharepoint -g
>>
npm WARN notsup Unsupported engine for got#5.7.1: wanted: {"node":">=0.10.0 <7"}
(current: {"node":"12.13.0","npm":"6.13.0"})
>>
npm WARN notsup Not compatible with your version of node/npm: got#5.7.1
>>
+ #microsoft/generator-sharepoint#1.9.1
updated 1 package in 8.851s
I have tried older versions of node.js but either they were too old for them to work with the new npm or they were too new to work with the generator.
Any help would be greatly appreciated. Thanks!
The current supported LTS version of NodeJS for the SharePoint Framework is both Node.js v8.x and Node.js v10.x. You need install Node.js for v8.x or v10.x.
Download Node.js: https://nodejs.org/en/download/releases/
I was also facing this issue. I found if Installed version 8.x.x of Node and then ran
npm install -g npm#5
This would lower the version of npm and allow me to install the generator.
I'm only getting started with Node and npm so have no idea what the impact of doing this is. However, it did work as I was able to run npm list -g --depth=0 and see the generator had been installed.
Related
I am getting this warning from github on my npm project build process...
I tried searching on the internet and also read the blog link posted by github - but I could not find the solution to it anywhere. Am I missing something ?
Warning seen
npm notice Beginning October 4, 2021, all connections to the npm registry - including for package installation - must use TLS 1.2 or higher. You are currently using plaintext http to connect. Please visit the GitHub blog for more information: https://github.blog/2021-08-23-npm-registry-deprecating-tls-1-0-tls-1-1/
After updating your NodeJS and NPM Version run this command in CLI
npm set registry=https://registry.npmjs.org/
Save your Life, Thanks me Later :D
I can solve the issue by the way:
First Step: npm set registry=https://registry.npmjs.org/
Second Step: npm install -g https://tls-test.npmjs.com/tls-test-1.0.0.tgz
Besides updating your version of node to an active or current LTS you want to ensure your NPM registry is set to an HTTPS endpoint:
registry=https://registry.npmjs.org/
You are facing that issue because your registry is set to HTTP version which is a bit insecure so the first thing that you should do is to put it to HTTPS version by running the following command below
npm set registry=https://registry.npmjs.org/
Then, after that you have to make sure your version of npm supports TLS 1.2, you can install a test package from an HTTPS endpoint that already has TLS 1.0 and TLS 1.1 disabled: by running this command below
npm install -g https://tls-test.npmjs.com/tls-test-1.0.0.tgz
You should see the following message:
Hello! The tls-test package was successfully downloaded and installed. Congratulations! Your package manager appears to support TLS 1.2.
If you don't see the message, don't worry you can try to install the package again, hope it will work out for you
Please make sure that you have latest(or somewhat recent) version of node installed on your system
To make sure that your version of npm supports TLS 1.2, you can install a test package from an HTTPS endpoint that already has TLS 1.0 and TLS 1.1 disabled:
npm install -g https://tls-test.npmjs.com/tls-test-1.0.0.tgz
You should see the following message:
Hello! The tls-test package was successfully downloaded and installed.
Congratulations! Your package manager appears to support TLS 1.2.
If you didn't see the above message, try to install some npm package.
If you didn't see the npm notice, you're good to go. If you happened to see again, please run the below command too.
npm set registry=https://registry.npmjs.org/
Source: The npm registry is deprecating TLS 1.0 and TLS 1.1
You are facing this issue because of your registry is still set to http version and that causing you this error. All You need to do is just Run following command in your terminal.
npm config set registry https://registry.npmjs.org/
and that is it!
now you can run any npm command
Well, I had several problems with node and npm. The one described in this question was only the last one.
I was not able to execute npm install, the node_modules were partially downloaded and at the end of the execution they were all deleted (the folder was visible, but it was deleted after running the command).
First problem: --location=global
First, I was getting this error message:
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead
Which I solved by following these instructions: https://stackoverflow.com/a/72592742/7389293
Apparently that allowed me to update to:
node -v: c16.16.0
npm -v: 8.17.0
Today's date: August 13, 2022.
Second problem: use TLS 1.2 or higher
Then, I still was having the error described in this question, which didn't allowed me to install the node_modules folder in my project:
npm notice Beginning October 4, 2021, all connections to the npm registry - including for package installation - must use TLS 1.2 or higher
The selected answer to the question made in the present screen your reading, finally fixed the problem: https://stackoverflow.com/a/70555822/7389293
After all of this I was able to run npm again, install all the packages from the package.json file, and run the website normally in the browser.
maxtimeout didn't work for me
so I tried converting to yarn by npm I -g yarn
and then yarn install in the root directory of the project(where I have to install the node_modules)
I trying to get the IBM Blockchain platform to work in Visual studio code (on Linux), but it keeps coming back with:
Could not rebuild native dependencies Failed to execute command "npm" with arguments
"rebuild, grpc, --target=6.1.5, --runtime=electron, --update-binary, --fallback-to-build, --
target_arch=x64, --dist-url=https://atom.io/download/electron" return code 1. Please ensure
that you have node and npm installed
I have node and npm installed
node -v
v10.17.0
and
npm -v
6.11.3
satisfying the constraints. I have visual studio code version 1.41.1. What could be thie issue?
The problem you are experiencing is described in this issue https://github.com/IBM-Blockchain/blockchain-vscode-extension/issues/1621
The issue is that there are no pre-built versions of grpc used by the fabric node sdk for electron 6 currently and due to changes in newer versions of gcc the grpc node module fails to compile when it falls back to using source because of no pre-built versions
The easiest solution is to downgrade for vscode 1.39 and install the extension.
Alternative options are to install gcc version 7 and make that the default in your linux environment or you could install a version of linux that has gcc version 7 as the default for example ubuntu 18.04 (which would allow grpc to compile from source)
I would like to know what is the best way at the moment to use PostgreSQL instead of MongoDb with MeteorJS.
I'm using meteor 1.8 and I found the package https://github.com/numtel/meteor-pg but to make it work i need this package : https://github.com/numtel/meteor-pg-server but when i install it i have this error :
meteor add numtel:pg-server
=> Errors while adding packages:
While checking for numtel:pg-server#1.0.1:
error: No compatible binary build found for this package. Contact the package author and ask them to publish it
for your platform.
I think it's not compatible with meteorJS 1.8 ...
So i found another package : https://github.com/Richie765/meteor-pg
And the problem with this one is when I install it, I have this error :
meteor npm install meteor-pg --save
added 26 packages from 47 contributors and audited 1904 packages in 5.961s
found 2 vulnerabilities (1 low, 1 high)
run npm audit fix to fix them, or npm audit for details
meteor npm audit fix
up to date in 2.264s
fixed 0 of 2 vulnerabilities in 1904 scanned packages
2 vulnerabilities required manual review and could not be updated
meteor npm audit
=== npm audit security report ===
Manual Review
Some vulnerabilities require your attention to resolve
Visit https://go.npm.me/audit-guide for additional guidance
High Cross-Site Scripting
Package bootstrap-tagsinput
Patched in No patch available
Dependency of bootstrap-tagsinput
Path bootstrap-tagsinput
More info https://nodesecurity.io/advisories/124
Low Prototype Pollution
Package lodash
Patched in >=4.17.5
Dependency of modernizr
Path modernizr > lodash
More info https://nodesecurity.io/advisories/577
I think this problem came because I'm using an Admin template which is : Angle - Bootstrap Admin Template (http://wrapbootstrap.com/preview/WB04HF123) because when i restart my project, there is the following error :
Unable to resolve some modules:
"jquery.flot.spline/jquery.flot.spline.js" in /C/Users/R-D/Desktop/meteor/imports/startup/client/vendor.js
(web.browser.legacy)
"jqueryui-touch-punch/jquery.ui.touch-punch.min.js" in
/C/Users/R-D/Desktop/meteor/imports/startup/client/vendor.js (web.browser.legacy)
If you notice problems related to these missing modules, consider running:
meteor npm install --save jquery.flot.spline jqueryui-touch-punch
so i execute meteor npm install --save jquery.flot.spline jqueryui-touch-punch then :
npm ERR! code E404
npm ERR! 404 Not Found: jquery.flot.spline#latest
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\R-D\AppData\Roaming\npm-cache_logs\2018-11-26T10_35_09_102Z-debug.log
I'm sorry if my problem is dumb, i'm a young developper and it's the first framework i'm using.
Best regards.
you can you use it with any database you want but you will lost the real meteor fell like real time data and other cool feature meteor have
you can use https://node-postgres.com/ for the installation and use Meteor.wrapAsync() for the operation
i try to install the hot reload module of jspm using the chokidar-socket-emitter. Installation works like charme, but after that it is not possible to start the watch task as described here: http://jspm.io/0.17-beta-guide/hot-reloading.html
Here is my install log:
XXXXXMacBookPro:dasding xxxxxx$ sudo npm i -g chokidar-socket-emitter
\
fsevents#1.0.12 install /usr/local/lib/node_modules/chokidar-socket-emitter/node_modules/chokidar/node_modules/fsevents
node-pre-gyp install --fallback-to-build
[fsevents] Success: "/usr/local/lib/node_modules/chokidar-socket-emitter/node_modules/chokidar/node_modules/fsevents/lib/binding/Release/node-v14-darwin-x64/fse.node" is installed via remote
chokidar-socket-emitter#0.3.1 /usr/local/lib/node_modules/chokidar-socket-emitter
├── socket.io#1.4.6 (has-binary#0.1.7, debug#2.2.0, socket.io-parser#2.2.6, socket.io-adapter#0.4.0, engine.io#1.6.9, socket.io-client#1.4.6)
└── chokidar#1.5.2 (path-is-absolute#1.0.0, inherits#2.0.1, glob-parent#2.0.0, async-each#1.0.0, is-binary-path#1.0.1, is-glob#2.0.1, readdirp#2.0.0, anymatch#1.3.0, fsevents#1.0.12)
XXXXXMacBookPro:dasding xxxxxx$ chokidar-socket-emitter
bash: chokidar-socket-emitter: command not found
XXXXXMacBookPro:dasding xxxxxx$
Does anyone has any idea why he is unable to find the command? i have no idea how to fix this, global installs always used to work without any problem.
thanks in advance
Ok, in case someone faces the same problem - my current node.js installation was unable to handle the latest version of chokidar-socket-emitter, so a lower version was installed, but the docs refered to the latest version, so there never was a command that could have been found. after updating my node.js installation everything worked like charme.
I am working on an Ionic 1 app with a remote team and lately our versions have not liked each other. I was wondering if the fact that I have also been working on Ionic 2 projects for whatever reason my CLI "thinks" these apps are also Ionic 2 and there for is shooting me the error below?
ionic build ios
WARN: ionic.project has been renamed to ionic.config.json, please rename it.
(node:9061) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
Uh oh! Looks like you're missing a module in your gulpfile:
Cannot find module 'bower'
Do you need to run `npm install`?
I have ran npm install.. does not make it go away.. I also have make sure to have bower installed.
What does this hold up here have to do with? I've been stuck here for a couple days now.
UPDATE
I went to an old project that and i tried to run ionic info to see the versions I have and system info but I get THE SAME error message..
I have no idea what I've done to get this...
mymac ~/code/92_AAC/newApp on master[!]
$ ionic info
WARN: ionic.project has been renamed to ionic.config.json, please rename it.
Uh oh! Looks like you're missing a module in your gulpfile:
Cannot find module 'gulp'
Do you need to run `npm install`?
UPDATE 2
I downgraded from Node 6 to Node 5.9 On the current project I was having the original issues.. I got this..
$ ionic build ios
******************************************************
Dependency warning - for the CLI to run correctly,
it is highly recommended to install/upgrade the following:
Install ios-sim to deploy iOS applications. `npm install -g ios-sim` (may require sudo)
Install ios-deploy to deploy iOS applications to devices. `npm install -g ios-deploy` (may require sudo)
******************************************************
WARN: ionic.project has been renamed to ionic.config.json, please rename it.
(node:11866) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
Uh oh! Looks like you're missing a module in your gulpfile:
Cannot find module 'bower'
Do you need to run `npm install`?
my ionic info(finally able to print it out)
Your system information:
Cordova CLI: 6.1.1
Gulp version: CLI version 1.2.1
Gulp local:
Ionic Version: 1.2.4
Ionic CLI Version: 1.7.14
Ionic App Lib Version: 0.7.0
ios-deploy version: 1.8.6
ios-sim version: 5.0.3
OS: Mac OS X El Capitan
Node Version: v5.9.1
Xcode version: Xcode 7.3.1 Build version 7D1014
UPDATE 3 after #janos suggestion
I ran npm install bower and it ran and installed some modules BUT I got the following..
click this link to see a screen shot of my command line in more detail
Screen Shot here!
```
$ ionic build ios
WARN: ionic.project has been renamed to ionic.config.json, please rename it.
(node:12122) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
There is an error in your gulpfile:
Error: ENOENT: no such file or directory, scandir '/Users/abelista/code/inov/cornerstone/inov/a4c/passengerApp/trunk/passenger/node_modules/gulp-sass/node_modules/node-sass/vendor'
at Error (native)
at Object.fs.readdirSync (fs.js:945:18)
at Object.getInstalledBinaries (/Users/abelista/code/inov/cornerstone/inov/a4c/passengerApp/trunk/passenger/node_modules/gulp-sass/node_modules/node-sass/lib/extensions.js:74:13)
at foundBinariesList (/Users/abelista/code/inov/cornerstone/inov/a4c/passengerApp/trunk/passenger/node_modules/gulp-sass/node_modules/node-sass/lib/errors.js:20:15)
at foundBinaries (/Users/abelista/code/inov/cornerstone/inov/a4c/passengerApp/trunk/passenger/node_modules/gulp-sass/node_modules/node-sass/lib/errors.js:15:5)
at Object.module.exports.missingBinary (/Users/abelista/code/inov/cornerstone/inov/a4c/passengerApp/trunk/passenger/node_modules/gulp-sass/node_modules/node-sass/lib/errors.js:45:5)
at Object. (/Users/abelista/code/inov/cornerstone/inoabelista
```
List item: The main error (A4CPassenger#1.1.1 - not sure what to call this.. but this was basically the name of the app? I believe the remote team changed it.. for whatever reason I am still getting the old name..)
I was running Node 6.0.0 and I needed to run Node 4.4.4
Under the above conditions can not be resolved, consider the ionic version, I encountered the same problem, because the final version ionic problem. ionic version upgrade quickly, do the project two months ago, and now ionic been upgraded from 1.7.16 to 2.0.0 of. if you Want to re-run this version, you should enter cmd 'npm install ionic#1.7.16', after the run is completed, then the implementation of 'ionic serve' you can run an older version of the project.
I hope to help you
I got the same situation.
I had updated ionic from npm (because it said it is outdated) and I didn't realize I have to update npm too. So I have to update npm e remove and reinstall ionic.
# Update npm (downloaded from nodejs.org +6)
sudo npm remove ionic
sudo npm install -g ionic
Run npm uninstall --save-dev gulp-sass#2