These are chat archives for systemjs/systemjs
I’m running into a problem using JSPM/SystemJS with TypeScript as the transpiler that makes debugging rather difficult. When importing modules into my app, runtime errors will cause the script to fail silently (no runtime errors).
I’m able to make this work with an extremely simple setup.
app.js is loaded from a barebones index.html (loads system.js, config.js, and imports app.js). app.js contains two lines:
import $ from ‘jquery’; console.log(undef_var);
Under these conditions, I see know errors in the Chrome dev tools, though errors reappear when I comment out the import statement. Code that’s free of runtime errors will work as intended and bring in the correct modules.
Any ideas? Debugging even a small script is quite a beast without any feedback from the compiler or runtime.
traceurin dependencies and no
I'm trying to understand what appears to be three module loader workflows:
Pointers to the second two would be appreciated, but here I'm mainly interested in es6-module-loader & systemjs (I already use jspm).
What are simple static workflows for these two? I presume using babel first to compile to require() would be the most logical? And possibly work with legacy modules that use require() & es5?