The current NPM support have several issues: - The current NPM fetcher downloads the dependency tree but not the other fetchers. The 'subdir' parameter was used to fix this issue. - They are multiple issues with package names (uppercase, exotic characters, scoped packages) even if they are inside the dependencies. - The lockdown file generation have issues. When a package depends on multiple version of the same package (all versions have the same checksum).
This patchset refactors the NPM support in Yocto: - As the NPM algorithm for dependency management is hard to handle, the new NPM fetcher downloads only the package source (and not the dependencies, like the other fetchers) (patch submitted in the bitbake-devel list). - The NPM class handles the dependencies using NPM (and not manually). - The NPM recipe creation is simplified to avoid issues. - The lockdown file is no more used as it is no longer relevant compared to the latest shrinkwrap file format. This patchset may remove some features (lockdown file, license management for dependencies) but fixes the majority of the NPM issues. All of these issues from the bugzilla.yoctoproject.org are resolved by this patchset: #10237, #10760, #11028, #11728, #11902, #12534 The fetcher and recipetool are now aware of a 'latest' keyword for the version which allow to build the latest version available on the registry. This feature fixes the two issues: #10515, #11029 Moreover the issue #13415 should also be fixed but I cannot test it. I have tested the recipe creation and builds using a self made example to generate build failures: - https://github.com/savoirfairelinux/node-server-example - https://npmjs.com/package/@savoirfairelinux/node-server-example The test steps are these ones: $ source poky/oe-init-build-env $ bitbake-layers add-layer ../meta-openembedded/meta-oe $ devtool add "npm://registry.npmjs.org;name=@savoirfairelinux/node-server-example;version=latest" $ devtool build savoirfairelinux-node-server-example $ bitbake-layers create-layer ../meta-test $ bitbake-layers add-layer ../meta-test $ devtool finish savoirfairelinux-node-server-example ../meta-test $ echo IMAGE_INSTALL_append = '" savoirfairelinux-node-server-example"' >> conf/local.conf $ bitbake core-image-minimal Also the 'devtool add' url could be one of these: - npm://registry.npmjs.org;name=@savoirfairelinux/node-server-example;version=latest This url uses the new npm fetcher and request the latest version available on the registry. - npm://registry.npmjs.org;name=@savoirfairelinux/node-server-example;version=1.0.0 This url uses the new npm fetcher and request a fixed version. - git://github.com/savoirfairelinux/node-server-example.git;protocol=https This url uses the git fetcher. As the dependencies are managed by the NPM class, any fetcher can be used. When this patchset will be merged, I have planned to update the NPM wiki: https://wiki.yoctoproject.org/wiki/TipsAndTricks/NPM This patchset is also the base work for the full Angular support in Yocto that I am preparing. These applications have a huge dependency tree which is ideal to test the NPM support. Jean-Marie LEMETAYER (6): npm.bbclass: refactor the npm class devtool: update command line options for npm recipetool/create_npm.py: refactor the npm recipe creation handler devtool/standard.py: update the append file for the npm recipes recipetool/create.py: replace 'latest' keyword for npm recipetool/create.py: remove the 'noverify' url parameter meta/classes/npm.bbclass | 210 +++++++++---- scripts/lib/devtool/standard.py | 22 +- scripts/lib/recipetool/create.py | 16 +- scripts/lib/recipetool/create_npm.py | 444 ++++++++++----------------- 4 files changed, 331 insertions(+), 361 deletions(-) -- 2.20.1 -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
