I have a new Macbook and i am trying to setup spfx environment in it for the first time. I tried to look up for the process but i run into one or the other issue.
Any help will be appreciated.
I tried to install nvm and node v14.15.0 since that is compatible for spfx and after that i am running into an issue Bad CPU type in executable while downloading other dependencies
Related
I am using gatsby cli, Suddenly gatsby develop command returning an error even if I create new site from scratch. I am using M1 macbook pro with big sur, is there anyone faced same issue? if yes how to resolve this?. I have configured everything properly by following official doc, am I missing something?
here is my terminal screenshot
Error:
macOS 11.2: Fatal error Check failed: allocator->SetPermissions
Parts of the stacktrace:
#
# Fatal error in , line 0
# Check failed: allocator->SetPermissions(reinterpret_cast<void*>(region.begin()), region.size(), PageAllocator::kNoAccess).
#
#
#
#FailureMessage Object: 0x16f986408
1: 0x100575758 node::NodePlatform::GetStackTracePrinter()::$_3::__invoke()
...
It seems a Node-related issue. According to this GitHub thread, try:
arch -x86_64 zsh
nvm install 14
nvm alias default 14
exit
All the solutions are related to the Node version. Remember to clean your cache by running gatsby clean and removing the node_modules in each trial.
As other threads points the issue seems to be related to the latest Node version. With the snippet above you'll roll back to version 14 as a temporal workaround while the issue is being fixed.
This was fixed in Node v15.9.0 If you installled using homebrew on a mac you can do brew upgrade node to get the latest version
Unfortunately the only solution is to revert to nodejs 14, using Rosetta.
Additional here's the issue in V8: https://bugs.chromium.org/p/v8/issues/detail?id=11389
No ETA. Everyone, please stop asking for when this will be resolved.
We know about the issue and are working on it.
Also note that Node.js is still not officially supported on
macOS+arm64. We do not produce binaries for it and you can use the x64
ones in the mean time.
https://github.com/nodejs/node/issues/37061#issuecomment-772559363
I fixed this issue by reinstalling node via nvm.
I had to open Rosetta 2 Terminal first.
nvm install node
nvm use node
After these commands.
I reinstalled packages using yarn command.
this way it worked.
This works... nvm install 16
Here's the nvm install docs... https://github.com/nvm-sh/nvm
System: CENTOS7
I'm working on our TEST system that has a version of node prior to 8.9.
The application which I'm working on uses node 8.9.
The application runs fine when deployed out to Tomcat.
The issue is that I'm unable to just run 'ng serve' because the system sees v6.x.x.
Is there a way that I can modify my project to see the packaged node v8.x so I can run the ng options?
I'm instructed to not modify the system settings.
UPDATE
Just so others know what I ended up doing was modifying my bash script to include in the PATH ./node_modules to where node was in the local project. This is always the same path for whatever project and its version on node.
I did that for a while until a few months ago when we finally had rights to do things differently and are now using Node Version Manager
Install nvm (node version manager) to centOS
Then you will can install many version of node in your system
In this case you have to alias default version of node in nvm setting with version you want
I was able to get node-printer to work on my local machine for my electron app to print this certain pdf I have. The issue is that when I build and package the app and install it on a different machine, it doesn't work. Do these other machines also need to have those dependencies of python and VS2013 that I needed to install the module? If so what would be the alternative be since I don't want my users to have install python, VS2013, and node gyp just to make printing work?
I'm having problem's when trying to run my gulp command in the terminal. I've been trying to track down the issue and from what I can tell the issue is that I'm running an outdated version of node.
node -v tells me that I am on v0.10.46, but the Node install downloaded from the website says it's currently on v4.4.7.
The first issue I had was with es6 promises, but I managed to install the es6-polyfill which solved the issue.
Now gulp is throwing an error related to /node_modules/gulp-imagemin/index.js. Specifically the use of const variables. (const path = require('path')).
Based on this thread: https://github.com/sindresorhus/gulp-imagemin/issues/181#issuecomment-219303510 - this issue seems to be an outdated version of node, but no matter what I do it won't upgrade!
I've explored all possible avenues for upgrading Node - using npm, nvm, n, brew and even a local re-install, but everytime it seems to be installing an outdated version.
I've explored the possibility that I'm installing a 32bit version on a 64bit system, but that doesn't seem to be the issue either.
I have absolutely no idea how to progress fixing this issue. I'm trying to build a wordpress website, and no matter what theme I use this error comes back to haunt me!
Help!
EDIT:
Just to add.. in this image (http://imgur.com/a/OzR5Y) you can see the output of me trying to upgrade using N, and then following the David Walsh upgrading method.
I had the same problem and I tried everything from uninstalling it by this instructions without any result. But maybe you have in your computer a management like nvm installed, just try this:
which node
And then if the respond of that is something like:
/Users/MYUSER/.nvm/v0.10.46/bin/node
That's the problem, so you can solve this by uninstalling nvm and then install Node.js normally or just keep using nvm
I installed Python 2.7 (had 3.4) and solved one error. Then, I installed Windows 7 SDK, solved another error, but no luck... I read here that I don't have to install Visual Studio as well... Can someone enlighten me with a solution?
The screenshots:
Assure this runs clean prior to your above install
npm install -g node-gyp
Do you have a c compiler installed ?
Are you creating a new nodejs app ? If so then issue this which will prompt you for details then cut a fresh package.json file for you :
npm init
In my opinion Windows is not the best for development , I have so much problems using Windows (and had the same problem), later I've switched to Ubuntu (just learn more Linux and C) - it has so much built-in programs so you don't have to install it by yourself (and you won't have any problems with that little problems and get even more knowledge).