There is likely additional logging output above. (/home/dr_nyt/.nvm/versions/node/v11.12.0/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)ġ3 verbose stack at ChildProcess.emit (events.js:197:13)ġ3 verbose stack at maybeClose (internal/child_process.js:988:16)ġ3 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:265:5)ġ4 verbose pkgid verbose cwd /home/dr_nyt/moodlemobiledirectoryġ7 verbose argv "/home/dr_nyt/.nvm/versions/node/v11.12.0/bin/node" "/home/dr_nyt/.nvm/versions/node/v11.12.0/bin/npm" "run" "setup"Ģ2 error setup: `npm install & npx cordova prepare & npx gulp`Ģ3 error This is probably not a problem with npm. (/home/dr_nyt/.nvm/versions/node/v11.12.0/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)ġ3 verbose stack at EventEmitter.emit (events.js:197:13)ġ3 verbose stack at ChildProcess. I am using Ubuntu 18.04 and issued the following commands:ġ verbose cli [ '/home/dr_nyt/.nvm/versions/node/v11.12.0/bin/node',ġ verbose cli '/home/dr_nyt/.nvm/versions/node/v11.12.0/bin/npm',Ģ info using info using verbose run-script ĥ info lifecycle info lifecycle verbose lifecycle unsafe-perm in lifecycle trueĨ verbose lifecycle PATH: /home/dr_nyt/.nvm/versions/node/v11.12.0/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/dr_nyt/moodlemobiledirectory/node_modules/.bin:/home/dr_nyt/.nvm/versions/node/v11.12.0/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/binĩ verbose lifecycle CWD: /home/dr_nyt/moodlemobiledirectoryġ0 silly lifecycle Args: ġ1 silly lifecycle Returned: code: 1 signal: nullġ2 info lifecycle Failed to exec setup scriptġ3 verbose stack Error: setup: `npm install & npx cordova prepare & npx gulp`ġ3 verbose stack at EventEmitter. I get an error when running "npm run setup". I'm fairly new to moodle and was trying to build an app from this repo: I'm not going into detail here (using the installer script and the tools is already well documented), but this is my goto choice, since it allows for simple upgrades and multiple versions. NVM is a great tool for installing and managing multiple versions of Node.js. I choose to do this, but it means I have to update my symlinks on installation of a new version of Node. ![]() You can also choose to create symlinks so they'll appear in your path: sudo ln -s `which node` /usr/bin/node ls-remote to see available versions and nvm install v15.2.1 to install nodejs version 15. You can override this by setting the path explicitly, like this: sudo env "PATH=$PATH" npm -g i some_module Latest version of node you can install for armv6 seems to be v11.15.0. This is because the default sudoers config uses a safe reset for the path. NOTE: if you install with this method, you may find that the node, npm, npx or any other binary commands installed via a global node module do not work correctly with sudo. This is the method I use on one of my older Pis, and I find that it makes upgrading fairly easy (though far more time-consuming that using nvm or apt). profile that can be used to switch the versions. You might prefer setting up Node this way, since it makes it slightly easier to install mutiple versions (as it puts each version of Node in a subdirectory of /usr/local/lib/nodejs and adds variables to. Another way to install the binaryĪn alternative method is described here. The downside of the above is that it doesn't put the /usr/local/node/bin directory on your path, so any binary commands that get installed when you do something like npm i -g cli-providing-package will require using the full path. Npm -v # Verifying that the npm install worked Node -v # Verifying that the Node.js install worked Sudo mv node-vX.X.X-linux-armv6l /usr/local/node The good news: you can still get up-to-date armv6 builds from the Unoffical Builds project, including the lastest v14.X LTS versions: See below for unofficial builds, which will keep your Node.js updated, patched, and supported, but avoids you having to build it yourself. ![]() At least that version will get support -including security updates- through April 2021. I recommend sticking with the v10.X/LTS Dubnium releases. The last version to get official builds for this platform was v11.x, which is now retired. ![]() Note: it looks like official builds for Node on Linux armv6 stopped with the v12.x releases. That said, there's a fantastic tool for the community called nvm that allows you to manage the versions of Node.js that you've got installed locally. This method works for all Raspberry Pi models, as long as the official distribution keeps building for armv6. By default, there's not a way to upgrade the version of Node.js you've got from within Node.js itself. You can download and install binaries of Node.js from. Unfortunately, NodeSource only build for armv7/armv8, so this won't work for Raspberry Pis that use armv6, like Pi 1 and the Pi Zero/Zero W. This method lets you pick a modern version of Node.js, and still use apt, so you can get updates pretty easily.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |