linux/poky.git/meta/classes/npm.bbclass, branch hardknott-next

npm.bbclass: avoid building target nodejs for native npm recipes

2021-02-12T23:32:16+00:00

The current recipe unconditionally RDEPENDS on nodejs (the target one). When building on the "-native recipe" of "BBCLASSEXTEND native" recipe, the target nodejs is unnecessarily built. This patch fixes this by only RDEPENDS on nodejs when building for the target. (From OE-Core rev: 92a9a86df9e3bcffb13d2f8b5dcbe7822170f734) Signed-off-by: Yoann Congal Signed-off-by: Richard Purdie

npm.bbclass: use python3 for npm config

2021-01-30T10:41:03+00:00

python2-native executable is not available in sysroot anymore, which causes compilation of some nodejs modules to fail. Switch to python3 as a default python version. (From OE-Core rev: d21f50ecf8e8683a92b7d234fa8225c2c1470595) Signed-off-by: Vyacheslav Yurkov Signed-off-by: Richard Purdie

npm.bbclass: make shrinkwrap file optional

2021-01-16T22:39:36+00:00

Some packages don't have shrinkwrap file which means no npmsw uri is provided in the recipe. (From OE-Core rev: 47760b0d7d66b2b68ee197d359f0b7b17374d742) Signed-off-by: Kamel Bouhara Signed-off-by: Richard Purdie

classes/npm: force to rebuild the prebuild addons

2020-01-27T16:48:09+00:00

This commit forces to rebuild the prebuild addons which are using node-gyp-build. https://www.npmjs.com/package/node-gyp-build (From OE-Core rev: dc4dda4d459ef66246cb7fb6f7d667c982707544) Signed-off-by: Jean-Marie LEMETAYER Signed-off-by: Richard Purdie

classes/npm: use the native python

2020-01-27T16:48:09+00:00

When building addons, the node-gyp build tool is looking for python. It is available in the native directory but not directly in the PATH. This commit configures npm to use the native python executable. (From OE-Core rev: 946fd69cba6f60c531ff34091cda3b7fee8ee594) Signed-off-by: Jean-Marie LEMETAYER Signed-off-by: Richard Purdie

classes/npm: use the local node headers

2020-01-27T16:48:09+00:00

When building addons, the node headers are needed to be able to compile properly. Usually they are downloaded by npm but network access in the do_compile task are unauthorized. Hopefully the local node headers are available in the native sysroot so lets use them. (From OE-Core rev: e4c111dacc808d8c7883f3a36dd5a9f65e7a44cc) Signed-off-by: Jean-Marie LEMETAYER Signed-off-by: Richard Purdie

classes/npm: restrict the build to be offline

2020-01-27T16:48:09+00:00

After the do_fetch task, every other tasks must not access the network. In order to ensure this point every npm command must use the offline configuration. In addition setting an invalid proxy is used as a safety. (From OE-Core rev: 1133f3ab485031df6e107f826b7398e5133f9c4d) Signed-off-by: Jean-Marie LEMETAYER Signed-off-by: Richard Purdie

classes/npm: refactor the npm class

2020-01-27T16:48:09+00:00

This commit splits the npm build in three steps: 1. With the new npmsw fetcher, the sources and dependencies of the package have been fetched and unpacked. As sources can also be patched, a local cache must be configured to use these modified sources. 2. Next, the installation process is run using the local cache only. Some packages may need to be compiled. 3. The final installation filters the previously installed files to avoid unnecessary files. This new version also fixes multiple issues related to npm dependencies badly handled: package names, scope packages, installation directories (From OE-Core rev: fb2252ee0777c6d26dea94c7588c323a6b97e961) Signed-off-by: Jean-Marie LEMETAYER Signed-off-by: Richard Purdie

npm: remove some temporary build files

2019-05-21T11:56:33+00:00

Fixes [YOCTO #11028] When dealing with node modules which use "node-gyp" [1] to build native addons to node. Some temporary build files stay in the image: object files, static library files, dependency files, ... This commit does not keep only the required files, but remove the files which can leads to QA issues (staticdev with static library files). [1]: https://github.com/nodejs/node-gyp (From OE-Core rev: bac9075f51f6acba2fcfbe9f79f97f5171186d9c) Signed-off-by: Jean-Marie LEMETAYER Signed-off-by: Richard Purdie

npm: fix node and npm default directory conflict

2019-05-21T11:56:33+00:00

Fixes [YOCTO #13349] When dealing with node modules which have declared "bin" files [1], npm will create a link in '/usr/bin' with a relative link to '../lib/node_modules/'. The commits e9270af4296ce2af292059617a717e42fc17425c and 2713d9bcc39c712ef34003ce8424416441be558e explicitely use '/usr/lib/node/' as install directory, but does not care about the "bin" symbolic linked files. In order to keep valid links, and to keep it as simple as possible, the path '/usr/lib/node_modules/' is used as install directory for npm. And a symbolic link is created to have a valid '/usr/lib/node/' path, needed for node. [1]: https://docs.npmjs.com/files/package.json#bin (From OE-Core rev: 2d72007deea7ed529f82b8a6e67e2715dd0a0dca) Signed-off-by: Jean-Marie LEMETAYER Signed-off-by: Richard Purdie