Bug 10517 - npm packaging does not create executable for application module
Summary: npm packaging does not create executable for application module
Status: RESOLVED DUPLICATE of bug 10460
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: devtools / tool chain (show other bugs)
Version: 2.3
Hardware: x86 Multiple
: Undecided normal
Target Milestone: ---
Assignee: Paul Eggleton
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-10-28 00:42 UTC by Henry Bruce
Modified: 2016-10-28 02:12 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Henry Bruce 2016-10-28 00:42:53 UTC
If you have an npm application module called say "my-node-app", when running "npm install my-node-app" a link to usr/bin/my-node-app is created. 
i.e. /usr/bin/my-node-app -> /usr/lib/node_modules/my-node-app/my-node-app.js

However devtool does not create this link when packaging the module so it cannot be run as 'my-node-app' and instead it must be started as 
node usr/lib/node_modules/my-node-app/my-node-app.js
Comment 1 Paul Eggleton 2016-10-28 02:12:49 UTC
Duplicate of bug 10460 (which I have a patch for, I just haven't sent it yet).

*** This bug has been marked as a duplicate of bug 10460 ***