Facing a hard time of "require" a node module in an experimental plugin

[jack4it]

I'm trying to write a systemjs plugin, but facing a hard time of "require" a npm module. The require always tries to resolve the node module from right at the root of the app, instead of node_modules folder. Why? How systemjs builder resolve the plugins and teach the plugins to load subsequent node modules?

It fails even this is the only line in my plugin.js. I have installed less both via jspm install npm:less and npm install less. By the way, is it possible to pass --no-optional through jspm install to npm install? The dependencies pulled in via jspm install npm:less is a little crazy... :(

var lessc = require("less");

E:\__prj\systemjs-test>node build.js
Build error
[Error: ENOENT: no such file or directory, open 'E:\__prj\systemjs-test\asap.js']

Thanks!

[jack4it]

Succeeded with :) Maybe should somehow document this as, at least a Tip

System._nodeRequire("less")

[jack4it]

I just realized, it is not just _nodeRequire is required to use here, but also the respective node module has to be installed by npm install...

Why can't systemjs load the modules installed by jspm install when executing in node? Now we have to duplicate the npm packages, if we have to use the package in both browser and node? :(

[guybedford]

@jack4it see https://github.com/jspm/jspm-cli/blob/master/docs/nodejs-usage.md for more info. Full server-side execution support is coming in jspm 0.17.