component-run
Advanced tools
Run (component.io) components with node
Experimental. Local dependencies are not yet implemented.
Let's say you have a component based application with a local component lib/my-component.
While developing you might want to run this component in node, but since the resolution of require calls in component differs from node, it will not behave as expected.
For example, if the local component depends on component/emitter and thus requires it with require('emitter'), this will fail when running in node because there is no emitter node module.
Using component-run, the require calls will be intercepted, and it will first try to resolve the module using the component resolution algorithm. Failing this, it will fallback to the native node require.
$ npm install component-run
component-run path/to/my-component.js
MIT
FAQs
Run component.io components in node
The npm package component-run receives a total of 0 weekly downloads. As such, component-run popularity was classified as not popular.
We found that component-run demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
Security News
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.