Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

This does not seem to work with JSPM anymore

See original GitHub issue

@frankwallis @aluanhaddad We’re currently having some critical issues, which I think are related to https://github.com/jspm/registry/pull/1040.

Basically, when installing tslib from NPM using JSPM v0.16.52, it seems to get confused about which file is an ES module and which isn’t. When we did a jspm install this morning, it somehow ended up creating a jspm_packages/tslib@1.5.js file containing this:

export * from "npm:tslib@1.5.0/tslib.es6.js";
export {default} from "npm:tslib@1.5.0/tslib.es6.js";

Where previously, it contained this:

module.exports = require("npm:tslib@1.5.0/tslib.js");

Also, we end up with "format esm"; at the top of jspm_packages/tslib@1.5/tslib.js, where before it was "format cjs";. This makes no sense to me, as that file is clearly not an ES module, and System.js refuses to load this file, unless we enable client-side transpilation - which we won’t.

I’m not really sure what is happening here, but it’s breaking everything for us, which is a rather big problem. Do you know what is going on here, and if so, can you provide a workaround until it’s fixed? We can’t update to the latest JSPM just yet, for various reasons, so we absolutely need this to work for JSPM 0.16.