Reusing require.js modules in Node.js with AMDrequire

Re:Reusing require.js modules in Node.js with AMDrequire by greggman on Wednesday May 21, 2014 @11:01AM (#7778591)

I don't know browserify well but I'd assume having a compile step is the part that sucks. If you can use require.js style until shipping time you can debug the actual code directly instead of the compiled code. You see each module in the debugger as its original file.

[ Parent | on HN ]

Re:Reusing require.js modules in Node.js with AMDrequire by jgillich on Wednesday May 21, 2014 @11:12AM (#7778640)

Source maps solve that issue, even though browser support isn't perfect yet.

[ Parent | on HN ]

Re:Reusing require.js modules in Node.js with AMDrequire by alistairjcbrown on Wednesday May 21, 2014 @11:31AM (#7778769)

+1 - this is why I love requirejs - lazy load modules in development, compile for QA and deployment.

Update: My other love for requirejs is that you don't need to use relative paths when requiring a module. Once you have a relative path, you can't change the location of either dependant or dependency. The require config lets you separate what you call the module from the location of the file.

[ Parent | on HN ]

Re:Reusing require.js modules in Node.js with AMDrequire by danabramov on Wednesday May 21, 2014 @12:51PM (#7779257)

I tried porting a project from Require to Browserify and I gave up because of relative paths issue.

[ Parent | on HN ]