Open dmitrylebedev opened 8 years ago
I don't see a reason not to. I'm considering a rewrite from coffeescript -> es6 at some point.
@leafo The error "cannot find module" happens because the package.json is incorrect. The file is located at dist/sticky_kit.js but the package.json "main" is set to sticky_kit.js. If you fix this, it'll at least be loosely compatible with webpack/es6.
Note that I see the correct value for main in the GitHub repo but not in the package.json fetched from NPM.
Until the latest package.json
is pushed to npm, you can use it as
import 'sticky-kit/dist/sticky-kit.js';
or
require('sticky-kit/dist/sticky-kit.js');
Do not publish to npm? @leafo
I was having a similar issue but via JSPM - import 'sticky-kit/dist/sticky-kit.js'; does solve my build process not finding the js file, even with the package.json pointing to sticky-kit.js (the correct file) When importing I get an empty object only while still running the build process (grunt) - If I stop the process and restart it all is well.
@leafo any chances to update package.json in NPM repository?
Hi! Do you plan support for ES6 modules?