I am trying to start my first ionic project based on VUE, following the steps on https://ionicframework.com/docs/intro/cli
I reinstalling nodejs, tried uninstalling ionic > npm cache clear --force > reinstall, as well as launching Visual Studio Code in admin mode. Keep getting same error below. I am out of options, any advice?
? Starter template: blank
√ Preparing directory .\myapp in 1.41ms
√ Downloading and extracting blank starter in 320.71ms
> ionic integrations enable capacitor --quiet -- myapp io.ionic.starter
> npm.cmd i --save -E #capacitor/core#latest
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
npm WARN ERESOLVE overriding peer dependency
npm ERR! code ECONNRESET
npm ERR! network aborted
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\User\AppData\Local\npm-cache\_logs\2022-07-18T02_58_39_592Z-debug-0.log
[ERROR] An error occurred while running subprocess npm.
npm.cmd i --save -E #capacitor/core#latest exited with exit code 1.
Re-running this command with the --verbose flag may provide more information.
Installing dependencies may take several minutes.
──────────────────────────────────────────────────────────────────────────────
Ionic Advisory, tailored solutions and expert services by Ionic
Go to market faster
Real-time troubleshooting and guidance
Custom training, best practices, code and architecture reviews
Customized strategies for every phase of the development lifecycle
Learn more: https://ion.link/advisory
──────────────────────────────────────────────────────────────────────────────
> npm.cmd i
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
npm WARN ERESOLVE overriding peer dependency
npm ERR! code ERR_SSL_DECRYPTION_FAILED_OR_BAD_RECORD_MAC
npm ERR! 13168:error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mac:c:\ws\deps\openssl\openssl\ssl\record\ssl3_record.c:677:
npm ERR!
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\User\AppData\Local\npm-cache\_logs\2022-07-18T02_59_54_033Z-debug-0.log
[ERROR] An error occurred while running subprocess npm.
npm.cmd i exited with exit code 1.
Re-running this command with the --verbose flag may provide more information.
I've had the same issue myself but not had much chance to do any digging in to why it's doing it yet but could be a breaking change in a newer version of Angular which the Ionic team haven't picked up on.
In the meantime (assuming you're using Angular), use:
ng serve and access it at http://localhost:4200.
I have followed these steps to install PWA.
But when trying to install build tools and configure the python dependency, we are facing this issue in windows 10.
gyp: binding.gyp not found (cwd: C:\Users\xxxx) while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: gyp failed with exit code: 1
And also we have tried the same steps in ubuntu system and it results the following error.
make: *** No targets specified and no makefile found. Stop.
How to fix this?
#ibm -
I'm getting following error while trying to publish loopback application on IBM Cloud using API Designer portal. Please help me understand why is it looking into Temp folder to publish the application and how I can bypass that. I keep getting resource busy or locked issue with apiconnect toolkit.
Here's the node, npm and apiconnect toolkit version I'm using currently. Please let me know if you need any additional details.
node - v8.9.4
npm - v5.6.0
apiconnect - v5.0.8.2 (apiconnect: v2.7.111)
Error publishing runtime: Command failed: npm prune --production npm
ERR! path
C:\Users\SUNNY~1.GOE\AppData\Local\Temp\0.6717806509437265-1517290270545\project\node_modules\cryptiles\node_modules\boom\package.json.1443453620
npm ERR! code EBUSY npm ERR! errno -4082 npm ERR! syscall rename npm
ERR! EBUSY: resource busy or locked, rename
'C:\Users\SUNNY~1.GOE\AppData\Local\Temp\0.6717806509437265-1517290270545\project\node_modules\cryptiles\node_modules\boom\package.json.1443453620'
-> 'C:\Users\SUNNY~1.GOE\AppData\Local\Temp\0.6717806509437265-1517290270545\project\node_modules\cryptiles\node_modules\boom\package.json'
npm ERR! A complete log of this run can be found in: npm ERR!
C:\Sunny\npm-cache_logs\2018-01-30T05_31_21_546Z-debug.log Error ID:
a055ee2d-8232-459b-bf62-f4340837a61b
As a simple step, first run this command from cli
apic stop all
and try the publishing loopbaclk application to IBM Bluemix.
In case, this does not resolve the issue, then the problem may be due to permission issues during the installation of APIC toolkit. Uninstall the toolkit do a fresh install of toolkit using '--unsafe-perm' option with the install command to overrides the permisson issues Here is the example
sudo npm install --unsafe-perm -g apiconnect
Try the publish with the new instance of API Connect and see if it resolves the issue.
I am trying to use Ionic 2 on Windows 7 x64 bit and got stuck when using ionic start command. I have tried to read tutorials and installation instructions but got no luck. Here's the details of my problem:
Found depreciation warnings during cordova and ionic installation:
https://postimg.org/image/vf3qn8z9b/
Then it shows errors using following command in ionic:
ionic start newProject sidemenu --v2
https://postimg.org/image/4vz80prq5/
context of my npm-debug.log:
9284 warn optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^1.0.0 (node_modules\chokidar\node_modules\fsevents):
69285 warn notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.0.15: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"ia32"})
69286 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Valid OS: darwin
69286 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Valid Arch: any
69286 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Actual OS: win32
69286 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Actual Arch: ia32
69287 verbose stack Error: node-sass#3.10.1 postinstall: `node scripts/build.js`
69287 verbose stack Exit status 1
69287 verbose stack at EventEmitter.<anonymous> (C:\Program Files (x86)\nodejs\node_modules\npm\lib\utils\lifecycle.js:255:16)
69287 verbose stack at emitTwo (events.js:106:13)
69287 verbose stack at EventEmitter.emit (events.js:191:7)
69287 verbose stack at ChildProcess.<anonymous> (C:\Program Files (x86)\nodejs\node_modules\npm\lib\utils\spawn.js:40:14)
69287 verbose stack at emitTwo (events.js:106:13)
69287 verbose stack at ChildProcess.emit (events.js:191:7)
69287 verbose stack at maybeClose (internal/child_process.js:885:16)
69287 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
69288 verbose pkgid node-sass#3.10.1
69289 verbose cwd C:\Users\Lime\newIonicProj
69290 error Windows_NT 6.1.7601
69291 error argv "C:\\Program Files (x86)\\nodejs\\node.exe" "C:\\Program Files (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
69292 error node v7.3.0
69293 error npm v3.10.10
69294 error code ELIFECYCLE
69295 error node-sass#3.10.1 postinstall: `node scripts/build.js`
69295 error Exit status 1
69296 error Failed at the node-sass#3.10.1 postinstall script 'node scripts/build.js'.
69296 error Make sure you have the latest version of node.js and npm installed.
69296 error If you do, this is most likely a problem with the node-sass package,
69296 error not with npm itself.
69296 error Tell the author that this fails on your system:
69296 error node scripts/build.js
69296 error You can get information on how to open an issue for this project with:
69296 error npm bugs node-sass
69296 error Or if that isn't available, you can get their info via:
69296 error npm owner ls node-sass
69296 error There is likely additional logging output above.
69297 verbose exit [ 1, true ]
Applied Solutions:
Installed nodejs 7.3.0 (current version as of now).
Note: I have tried to install x64 bit but since I got errors, so I switched to x86 version and still no luck. I have also tried to downgrade nodejs to 6.9.2 and v4.4.7 but have made no progress at all.
Upgraded npm using "npm install -g npm", clear cache and update registry
Tried to rebuild node-sass
Tried to install minimatch, uuid and fsevents manually
Any idea, what I missed during the installation? I got same problems when creating projects using ionic version 1.
After series of uninstalling and installing the all dependencies, I found out that the problem occurred because of the incompatibility of node-sass to the current version of nodejs. I have solved the problem by:
installing x86 nodejs version 7.3.0
install cordova and ionic (not beta)
updated node-sass "install -g node-sass"
built node-sass again by using the command "npm rebuild node-sass"
After that, the when I tried to run "ionic serve" command, an error occurred. The error message was:
"Ionic serve error: Error: ENOENT: no such file or directory, open
'/home/.../IonicTest/www/index.html'"
run the command "npm run build" reference:
And cheers! It's already working :D
Yes, node 7 requires node.sass v13.12.0 or higher
69288 verbose pkgid node-sass#3.10.1
69289 verbose cwd C:\Users\Lime\newIonicProj
69290 error Windows_NT 6.1.7601
69291 error argv "C:\Program Files (x86)\nodejs\node.exe" "C:\Program Files (x86)\nodejs\node_modules\npm\bin\npm-cli.js" "install"
69292 error node v7.3.0
Check supported versions here : https://github.com/sass/node-sass/releases?after=3.4.0-RC1
Here's what I've done so far on my x64 OS:
Installed Python (v2.7 --specifically 2.7.6) and added it to the system path (C:\Python27)
Installed MS VS C++ 2010 Express Version (I already had VS 2012 but without the C++ component)
Installed the compiler update for Windows SDK 7.1
Successfully executed node-gyp configure (from my add-on directory under nodejs\node_modules where binding.gyp is located)
ran node-gyp build (as administrator)** This is what crashed, leaving me with:
this error:
C:\Program Files\nodejs\node_modules\msnodesql>node-gyp build
gyp info it worked if it ends with ok
gyp info using node-gyp#0.12.2
gyp info using node#0.10.25 | win32 | x64
gyp info spawn C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe
gyp info spawn args [ 'build/binding.sln',
gyp info spawn args '/clp:Verbosity=minimal',
gyp info spawn args '/nologo',
gyp info spawn args '/p:Configuration=Release;Platform=x64' ]
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
LINK : fatal error LNK1181: cannot open input file 'kernel32.lib' [C:\Program Files\nodejs\node_modules\msnodesql\build\sqlserver.vcxproj]
gyp ERR! build error
gyp ERR! stack Error: `C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe` failed with exit code: 1
gyp ERR! stack at ChildProcess.onExit (C:\Users\RNelson\AppData\Roaming\npm\node_modules\node-gyp\lib\build.js:267:23)
gyp ERR! stack at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:797:12)
gyp ERR! System Windows_NT 6.1.7601
gyp ERR! command "node" "C:\\Users\\RNelson\\AppData\\Roaming\\npm\\node_modules\\node- gyp\\bin\\node-gyp.js" "build"
gyp ERR! cwd C:\Program Files\nodejs\node_modules\msnodesql
gyp ERR! node -v v0.10.25
gyp ERR! node-gyp -v v0.12.2
gyp ERR! not ok
Any ideas as to what is going on?
I had a similar problem. I found that this switch helped me
--msvs_version=2012
so for example
npm install --msvs_version=2012 <package>
npm config set msvs_version 2013 --global worked for me as I use VS node tools and you dont need to specify msvs_version each time you do an npm install.
I had an issue whereby npm's config (c:\Users\username\ .npmrc) has an entry msvs_version=2012 which was out of date.
After spending a while to get this to work (for me accepted answer didn't work, for me it's just half solution) i did following:
Sadly, you must have visual studio (i installed express edition 2013
for DESKTOP)
Installed python 2.7.3 (you don't have to set any environment
variables)
Run cmd as administrator and go to you project root (where is you
package.json file)
First run: npm config set python C:\Python27\python.exe
Then: npm install -msvs_version=2013
The trick is in command npm config set python ...path_to_python_exe... which will be provided by npm to dependency which needs python i guess. I don't know why setting python as env variable is not enough.
If all above did not work (my case - Windows10 64bit)
Delete C:\Users\user_name\.node-gyp
Delete %AppData%/npm
Delete %AppData%/npm-cache
And install node-gyp again
Following instruction on node-gyp page
I chose Option 1 npm install --global --production windows-build-tools
For installing node-gyp in windows or any other OS
First you may have to download the node-gyp by
$ npm install -g node-gyp-install
Then install by
$ npm install -g node-gyp
you may need to do the above procedure as root/administrartor.
I had this same error now in 2015 when trying to install Keystone and I ran through all you told me but it didn't work on it's own. At the end, I just had to run the command
"C:\Program Files\Microsoft SDKs\Windows\v7.1\bin\SetEnv.CMD" /Release /x64
to set up the environment before running the command. (Don't freak out when it turns your window text green, it's working). So yeah I'd do the installations and set up environment variables in the same way everywhere on the internet suggests but make sure to run the above command before running any other command. It probably won't be useful to you, but hopefully it's useful to someone else. If that still doesn't work, MSVS version 2010 worked for me, so install that version and use the flag -msvs_version=2010 when running the npm command.
For me the solution that worked with VS express was to simply install Visual Studio 2013 Express for desktop (which is the only one that gives you a developer command prompt as of 2013 version). Open developer command prompt (elevated) and run NPM install commands. This did not require any special --msvs_version arguments, it just worked.
I came across this problem myself, and this is how I solved it using Visual Studio 2010:
Install following packages
Python 2.7+
Visual C++ Studio 2010 Express
Windows SDK 7.1 Note: If you get error on installation, maybe this link will help you.
Visual Studio 2010 SP1
Visual C++ 2010 SP1 Compiler Update for the Windows SDK 7.1
Use npm install from the Windows SDK command prompt (you need this because it sets additional environment variables).
Source: node-gyp instructions for VS2010
For me (Windows 7 64bit),
I struggled with this issue for half of a day Finally It worked.
On my way :
At control panel, I deleted all Python, Microsoft Visual Studio, Microsoft Redistributable, and something about I installed to solve this.
Window Update and restart.
Installed Python27, and Visual Studio 2013 with no setting env-val
npm install node-gyp -g
I got an error same thing, but after npm config set msvs_version 2013 --global , It works.
there is an easy to use windows build tools global node package. You could try this.
I was also getting similar issues and here is what worked for me.
Removed Python and Visual Studio
Installed Python 27 and Microsoft Visual Studio with "Desktop development with C++"
Setting the python path npm config set python /path/to/executable/python
npm install node-gyp -g
node-gyp configure --msvs_version=2013
Just had the same problem. Install NVM (Node version manager) and then open your CMD and use NVM install node# followed by the version your dependencies need. If you don't know what version you might need try playing around with different version I reverted my Node back to version 14.15.0 and then used NPM install and everything ran smoothly! Hope this helps!
Install chocolatey in PowerShell with administrator permissions:
Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1'))
Install required versions of the Microsoft Build Tools for Visual Studio:
https://community.chocolatey.org/packages?q=visual+studio+tools
In my case:
choco install visualstudio2019buildtools
And install workload:
cinst visualstudio2019-workload-vctools
Worked with node 16.16.0
If used nvm. Reinstall node version. And all will work fine.