dist directory missing

[docbf]

Hi, I added the master branch to my yocto project. Fetching and compilation worked without issues, but when I deploy the result to my target system and run node.js I get this error:

internal/modules/cjs/loader.js:430
      throw e;
      ^

Error: Cannot find module '/usr/lib/node/socket.io/dist/index.js'
    at createEsmNotFoundErr (internal/modules/cjs/loader.js:842:15)
    at finalizeEsmResolution (internal/modules/cjs/loader.js:835:15)
    at resolveExports (internal/modules/cjs/loader.js:424:14)
    at Function.Module._findPath (internal/modules/cjs/loader.js:464:31)
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:802:27)
    at Function.Module._load (internal/modules/cjs/loader.js:667:27)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at Object.<anonymous> (/www_update/main.js:8:12)
    at Module._compile (internal/modules/cjs/loader.js:999:30) {
  code: 'MODULE_NOT_FOUND',
  path: '/usr/lib/node/socket.io/package.json'

Looking at the repo I can not find the /dist/ directory as well. I reckon that I overlook something...

[darrachequesne]

Hi! The dist/ folder is not committed, you'll need to run npm run compile to create it (the TypeScript sources will be compiled to JavaScript).

socket.io/package.json

Line 40 in 2f96438

"compile": "rimraf ./dist && tsc",

[docbf]

Thanks for the quick reply. That makes sense. Unfortunately this does not seem to be run when I build it through Yocto/Bitbake or devtool. Do I have to add this manually to the recipe probably?

[docbf]

Ok, I managed to get it to work. The trick was to use the Registry Module Approach with devtool instead of the projects code approach. Means using devtool add "npm://registry.npmjs.org;package=socket.io;version=4.4.1" instead of devtool add https://github.com/socketio...
That created successfully the /dist directory and copied it on the target system. Don't know why the git approach did not work in this case, as other npm packages do work like this. But I am glad that it is up and running now.