5 ms·
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
by greggman 12y ago
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.
- jgillich 12y agoSource maps solve that issue, even though browser support isn't perfect yet.
- alistairjcbrown 12y ago+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.
- danabramov 12y agoI tried porting a project from Require to Browserify and I gave up because of relative paths issue.