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
dynamic import is stage 4 (but still doesn't work) #1339
Comments
We're currently waiting on support from ESLint for dynamic import. See this issue: eslint/eslint#11803 And here's a in-progress PR: eslint/eslint#11983 Once that's been released, we'll update and finally get support :) In the meantime, you can use |
sorry, yeah, I wouldn't have assumed it was your issue. however, searching the error message led to the closed issue where you kind of implied you'd fix it if it was in stage 4 😄 it sounds like the only purpose this issue serves is as a nag to merge the eslint version when it's released. (but maybe it feels good to close issues so I won't close it myself) |
Happy to leave this issue open as a reminder to watch the ESLint issue :) |
I just did a quick check, should this be working now? seems like everything got merged in |
@dtudury In order to get support, we need to update to ESLint 6.2.0 or later. There's a PR for that here: #1376 but it is blocked on this bug in
Once that's resolved, I'll update the version. |
Fixed in standard@14.1.0 |
What version of standard?
13.1.0
What operating system, Node.js, and npm version?
macOS 10.14.1, v10.16.0, 6.9.0
What did you expect to happen?
works on 83.29% of browsers and is in stage 4 of the TC39 process.
I expect standard to consider it valid code
What actually happened?
I know this has been reported before (#751) but that issue is closed and locked (because dynamic import was stage 3... but now it's stage 4)
The text was updated successfully, but these errors were encountered: