-
-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
summary.js import statements causing error #36
Comments
Same here node: '7.2.1', |
|
Works fine on v8.5.0 |
@fungilation Upgraded to |
Curious, try switching to my fork? I don't want some PRs merged to |
I'm on node 8.7.0 - this doesn't work yet without enabling module support and using a .mjs extension. Anyways @jbrooksuk are you open to accepting a pr which builds and publishes the transpiled source? |
I'm not sure what's the cause of import issues. I'm on node 8.7 and using in my React Native app without issue. For reference in debugging, this is my
$ react-native info
|
@fungilation this is because you are transpiling the source with babel. It breaks with pure node. Try it in a project that doesn't transpile. |
the same problems here |
I just tried with the master branch today, and got the same error. |
@jbrooksuk would you accept a PR changing to point at the transpiled js? |
My workaround is that I created my own local module with rollup. |
For anyone interested, as a quick fix I just transpiled it to a local file with a basic webpack config
Save this to webpack.config.js and run |
You need to ship the transpiled code in the published module rather than the raw code. babel won't transpile code under the node_modules folder by default so it needs to be done by the library publisher before publishing to npm. |
let _ = require('lodash')
let Tokenizer = require('sbd')
let request = require('request') |
I created a pull request fixing this issue(#50). You can use that instead the main package by using the command (or just wait him fix the issue / or merge the PR): |
The import statements in the summary.js causing error:
node version: v6.11.1
The text was updated successfully, but these errors were encountered: