Distribute as an ES6 Module about jsonexport HOT 5 CLOSED

@rjsteinert, you are way off point and assuming much...

Here, one line of code from this package: package.json babel build step

That one line of code is babel compiling to old browser code... Nothing TypeScript

TypeScript? I import this package using TypeScript but ...... Listen, just import that damn thing. I made it browser universal and now this is several messages deep on a subject you could have just tried out and found if it did or did not work.....

It works... Next. Close this

from jsonexport.

Yes, and I put a lot of work into that... The readme docs covers it. Just search "browser" at readme file

from jsonexport.

Ok, the code is ES6 compatible but it is NOT one flat file .min bundle file for direct browser stand alone usage.

It is expected that most everyone uses a code bundler these days. You could use bable yourself to bundle this code to one flat file.

The master branch of this package is intended for inclusion via npm package.json dependency declaration. I don't want to maintain some CDN branch for just one file for this edge case.

Good luck. Fare well

from jsonexport.

Hi @AckerApple - That's cool you can use this in TypeScript. The TypeScript transpiler must have support for the CommonJS Module standard you are using. Unfortunately that does allow us to import your module in our ES6 code without some extra build steps.

from jsonexport.

No worries man. I'm referring to ES6 modules in the browser with are not compatible with the node.js require method (CommonJS) for including dependencies that is being distributed in your package.

from jsonexport.