On 12/24/24 11:19, picca wrote:
Hello,

with the upstream build it works out of the box, this is a great news.

Now I am switching to the Debian Javascript team way and I end up with this message during the build

make[1]: Entering directory '/<<PKGBUILDDIR>>'
dh_auto_build --buildsystem=nodejs
/!\ examples/embed-amd/package.json not found
Unable to load examples/embed-amd
./lerna.json found

workspaces field found in package.json

Found debian/nodejs/additional_components
Adding component(s): packages/base
Adding component(s): packages/base-manager
Adding component(s): packages/controls
Adding component(s): packages/html-manager
No build command found, searching known files


The upstream use jlpm build with is doing

Hi,

packaging things in Debian means use available dependencies. The "jlpm build" command launch yarn to download dependencies during build. Yes it works but this is not valid for a package build.

See the build of jupyterlab to see how we succeed to build it using only Debian packages.

Best regards,
Xavier

--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Reply via email to