-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
No mutable exports error #660
Comments
Can you provide the code it's erroring out on? |
Sadly I cannot. The codebase is fairly big and more importantly proprietary. Based on the error I'm thinking if it wouldn't make sense to have handle |
It would be really helpful to have a MVP / example of the error. Even if your codebase is big and proprietary, you could do the following to help us fix this (while maintaining the privacy of your codebase):
In the case of this rule, it's very likely that you'll end up with a very short code example which will not betray any sensitive information about your project :) If you find the time to do this, that'd be awesome! |
I'm pretty unfamiliar with EScope, but @NullDivision is right that I goofed around with a few weird syntaxes (undeclared / unbound identifiers) and couldn't reproduce the error, but I suspect the change in bfdc2bb should resolve this. Would still love a repro case, if you can manage it. 😅 |
@benmosher Hi, I have a way to reproduce this w/ v2.2.0. In this commit I work around the issue. keybase/client@199bb2a If left as the commit before then it'll give the above error. |
@benmosher Is it possible to get a minor bump release for this? The referenced commit fixes it. I believe it's caused by using the
Caused by code similar to: type Foo = {};
type Bar = {};
export type {
Foo,
Bar,
}; |
I having this issue with a file I use for flow types File:
.eslintrc
please help! |
This tests the bug reported in issue import-js#758, which was actually already fixed in PR import-js#660.
I've got a PR (#835) that adds a test for this :) |
published! |
I get the following error when running version
2.2.0
:The text was updated successfully, but these errors were encountered: