I'm on a Raspberry pi 4. In my package.json I have:
"#sentry/browser": "^5.19.2",
"#sentry/node": "^5.19.2",
When I attempt to execute npm i with an ARM processor it won't build. It gives the error
Error: Command failed: /var/www/website/node_modules/#sentry/cli/sentry-cli --version
/var/www/website/node_modules/#sentry/cli/sentry-cli: 1: ELF: not found
/var/www/website/node_modules/#sentry/cli/sentry-cli: 2: Syntax error: ")" unexpected
This is due to the fact that sentry-cli does not have an ARM build. Here is a GitHub issue on that fact and the way you can build sentry-cli on your own. So I have built it and have the binary in my user folder. But I have no idea how to get it to look for that binary when run npm i
I tried to provide the path to my binary folder in the dependencies array, but that doesn't work since it's not a package and doesn't have its own package.json file. Any idea on how to install Sentry on an ARM?
Related
So I've made the big mistake of updating npm and node from versions 3.10.10 and 6.10.2, respectively to 5.6.0 and 9.3.0
Now my app doesn't work so I am getting quite desperate here. When I attempt to run it, I get the following error:
/Users/me/Workspace/MyApp/node_modules/node-sass/lib/binding.js:13
throw new Error(errors.unsupportedEnvironment());
^
Error: Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (59)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v4.5.3
I've looked up the error and haven't found much, except deleting the node_modules folder and doing npm install. Neither of which work. This now gives me the following error:
node-pre-gyp ERR! Tried to download(403): https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v3.1.8/node-v59-darwin-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for sqlite3#3.1.8 and node#9.3.0 (node-v59 ABI) (falling back to source compile with node-gyp)
ACTION deps_sqlite3_gyp_action_before_build_target_unpack_sqlite_dep Release/obj/gen/sqlite-autoconf-3150000/sqlite3.c
TOUCH Release/obj.target/deps/action_before_build.stamp
CC(target) Release/obj.target/sqlite3/gen/sqlite-autoconf-3150000/sqlite3.o
I am not sure where to go from here but am not getting desperate. What is going on? Is there anything I can do or should I just reverse to a previous version of node and npm?
You'll need to run npm rebuild, because Node-sass uses C++ addons, and that command
runs the npm build command on the matched folders. This is useful when you install a new version of node, and must recompile all your C++ addons with the new binary.
There's probably also no reason not to update node-sass to the current release 4.7.2.
Have a look at another handy package called ncu that can help you bulk-upgrade your package.json. Don't do it carelessly, you may create instability, but it's a handy start if you have a small number of specified dependencies.
I used npm for several months.
But after I install python/django and virtual environment, it's not working anymore.
The error is smething like this.
sudo npm install -g react-native-cli
module.js:341
throw err;
^Error: Cannot find module './cache/caching-client.js'
I used npm for several days but this happened first time. I searched to solve issue and found this link
Installing MEAN Stack: npm -v module.js: 338 throw err; Error: Cannot find module './cache/caching-client.js'.
But not working.
echo $NODE_PATH
/usr/local/lib/node_modules
And it occurs on all npm commands.
npm -v
npm init -y
I reinstalled the node.js again and it worked.:)
f you added React Native manually to your project, make sure you have included all the relevant dependencies that you are using, like RCTText.xcodeproj, RCTImage.xcodeproj. Next, the binaries built by these dependencies have to be linked to your app binary. Use the Linked Frameworks and Binaries section in the Xcode project settings. More detailed steps are here: Linking Libraries.
If you are using CocoaPods, verify that you have added React along with the subspecs to the Podfile. For example, if you were using the , and fetch() APIs, you would need to add these in your Podfile:
for more see this
https://www.npmjs.com/package/react-native-winjs-cli/tutorial
I am attempting to install the node.js module 'javascripting' (source code can be found: https://github.com/sethvincent/javascripting) and have been unable to install it as a global variable to run through the terminal.
After installing node.js I attempted to install javascripting with the line: npm install --global javascripting
While it is my understand that this should work, it only downloads the module but does not set it as a global variable to be run in terminal.
The error I receive when attempting to run it as a global variable is "/usr/bin/env: node: No such file or directory".
After receiving this error I attempted to move the module to /usr/bin/env from the directory it installed in (usr/local/lib/node_modules/javascripting). Unfortunately, I was not able to move the files because /usr/bin/env is not a directory, rather it seems to be some sort of executable java file (usr/bin is a directory).
I am a bit lost and would love some advice on either how to install the module as a working global variable or whether there is another way to run the module without installing it as a global variable.
This will happen if the node.js binary (node) is not installed in the $PATH anywhere.
if you run env node by itself, you will get the same error. It looks like this may be an Ubuntu bug: https://github.com/joyent/node/issues/3911
Try sudo ln -s /usr/bin/nodejs /usr/bin/node - that will symlink the node.js binary from the name Ubuntu gave it to the name it's supposed to have.
EDIT:
As mscdex pointed out in a comment (and as mentioned at the end of the bug I linked), there's a legacy package you can install that should create this symlink.
sudo apt-get install nodejs-legacy
The bug I linked above indicates that there are probably other problems with Ubuntu / Debian's default node.js package, and recommends you install your own either from the PPA mentioned there or from source.
You'll probably need to follow the advice in NPM modules won't install globally without sudo as well.
I am trying to reinstall node. I was screwing around a little bit trying to download a newer version.
So to uninstall I cleared out the node and node_module parts inside usr/local/bin/ and usr/local/src
Following these instructions
https://github.com/joysent/node/wiki/Installing-Node.js-via-package-manager#ubuntu-mint
When I run
xx.x#x:~/src/node-v0.10.18$ checkinstall
I get
dpkg: regarding .../node_0.10.18-1_i386.deb containing node:
nodejs conflicts with node
node (version 0.10.18-1) is to be installed.
node provides node and is to be installed.
dpkg: error processing /home/hassan/src/node-v0.10.18/node_0.10.18-1_i386.deb (--install):
conflicting packages - not installing node
Errors were encountered while processing:
/home/hassan/src/node-v0.10.18/node_0.10.18-1_i386.deb
(END)
I am not sure what else I should be doing. I tried a few other things.
:(
More details
This is what shows up on the command line
Copying files to the temporary directory...OK
Stripping ELF binaries and libraries...OK
Compressing man pages...OK
Building file list...OK
Building Debian package...OK
Installing Debian package... FAILED!
*** Failed to install the package
Do you want to see the log file? [y]: y
*** SIGINT received ***
Restoring overwritten files from backup...OK
Cleaning up...OK
Bye.
OH I solved it! I deleted all of the node related files through synaptic !! :D!
You may be able to use my pre-built packages which are available here:
https://launchpad.net/~chris-lea/+archive/node.js
They install a /usr/bin/nodejs binary and then create a symlink from that to /usr/bin/node.
If you are going to use these, be sure to remove any vestiges of any previous installs so that the system is using the correct binaries.
I have got a Nodejs app on AppFog and want to connect to a ftp-server with this.
I did install it with npm install ftp using "Ruby Command Prompt"
This is the only code line:
var FTPClient = require('ftp');
Trying to start the app, it throws an error:
Skipping npm-support: npm-shrinkwrap.json is not provided
Which kind of server should I use or what's the problem?
Still doesn't start:
Starting Application 'test007': .
Error: Application [test007] failed to start, logs information below.
====> /logs/staging.log <====
# Logfile created on 2013-03-09 10:37:09 +0000 by logger.rb/25413
Installing dependencies. Node version 0.8.14
Installing ftp#0.2.9 from local path
Installing xregexp#2.0.0 from local path
Installing node#0.0.0 from local path
Installing nodejs#0.0.1 from local path
But no error is shown.
Thanks in advance
The quick fix is to type npm shrinkwrap, which will provide an npm-shrinkwrap file.
A shrinkwrap file fixes the exact versions of your dependencies, and the exact version of their dependencies, and so on. Without it, each usage of npm install could install different versions of the packages -- sometimes, just different bugfix versions (1.4.2 vs 1.4.3), but sometimes much greater differences. There's no guarantee that your code will work with different dependency versions (in fact it is not uncommon to break), so shrinkwrapping is a great idea for any production-level code.
If you want to 'unshrinkwrap', just delete the npm-shrinkwrap.json. You can re-shrinkwrap at any point.