Hi Simon,
thank you - in my current solution I don't use npm bbclass at all.
I basically use npmsw://${THISDIR}/${BPN}/npm-shrinkwrap.json;dev=True
this will downloadall npm stuff including angular because of dev=True to
$S/node_modules
do_compile () {
# build frontend
chmod -R a+w
Sure, please find the bbclass file attached to this mail. All it does is
to inherit npm and overwrite configure with an extended copy .
Meanwhile, I saw another issue popping up: It seems that multiple
indirect dependencies to a package with different versions create
inconsitent license
Hi Simon,
I'm dealing actually with the same problem. Would you like to share your
"configure in my own subclass"?
I'm also thinking there is a need for a bbclass which actually is not using
gyp, instead it should be able to "npm run build".
There is alsa a patch for speeding up npm npmsw
Hi,
Am 12.02.21 um 11:12 schrieb Josef Holzmayr:
Howdy!
Thanks for sharing, a few comments inline.
Am Fr., 12. Feb. 2021 um 11:03 Uhr schrieb Simon Vogl :
I have some remarks and questions about the npm/nodejs support in dunfell that
I wanted to share. We are creating nodejs-based IoT edge
I have some remarks and questions about the npm/nodejs support in
dunfell that I wanted to share. We are creating nodejs-based IoT edge
solutions and upgrading our build environments to Dunfell one by one. In
the course of this, we are switching to the new npm-implementation and
found a few
