-
I had a modest goal for today, to understand how ES6 modules work and have a simple Hello World app that demonstrates.
I've tried to work my way through a bunch of tutorials, the only one that I f…
-
Most people author their code as es modules now, and many browsers can load them natively.
I'd like to write my tests as es modules as well, and just run them out of the box with karma without any …
-
Currently, running module-deps on source with ES6 module syntax throws `Error: Parsing file /blah/dee/dah.js 'import' and 'export' may appear only with 'sourceType: module' (4:0)`.
The reason for thi…
-
-
_From @dominicbarnes on November 28, 2016 7:38_
The more time goes on, the more I'd like to investigate using ES6 modules, rather than CommonJS. This would drastically affect the internals of this pl…
-
This will probably require to not concatenate the JS files. However can solve some no-undef Codacy issues and make the code more cleaner.
-
Currently we are generating invalid ES6 code. We should only have one export. Maybe we can generate 2 separate things for Node.js and Browser scopes respectively?
-
I like a lot of the features in Earl Grey, but one feature that I feel is lacking is proper support for ES6 modules.
My intention is to write client-side browser applications. I know that I can use W…
Pauan updated
8 years ago
-
I would like to request the new feature to add support of ES6 Modules, which are becoming the de-facto standard to package JavaScript code.
This would allow to use `fast-memoize` natively in modern…
-
The project website and npm page (in usage examples) suggests that the package is distributed in es6 module format, but that doesn't seem to be the case.
Doing `npm install --save ttag` and putting `…