-
Notifications
You must be signed in to change notification settings - Fork 743
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
New: ESLint v4 #241
New: ESLint v4 #241
Conversation
Been thinking about removing ESLint v1/v2 too. I'm currently undertaking a generic cleanup of ASTExplorer, if you want, I can remove them as part of it too. |
I'd advocate for hiding them from the menu, but not completely removing them. Older shared snippets might rely on them. I guess the general question is: Do we want to make old snippets continue to work and/or is it worth it? That's one of the reason why I started working on #197. |
Sounds good. |
if it's not that hard to maintain can just leave it unless someone really wants to remove? |
@hzoo Yeah but they contribute to the chunks sizes, and keeping them means periodically ensuring that they don't bloat up chunks with important JS and that they + their deps are loaded only on-demand.
@fkling Should we make this a poll on Twitter or something? |
Btw, are there any major API incompatibilities for plugins between ESLint v1..v4? Or can we just auto-switch to the new ESLint for old snippets? |
We dont use plugins in here, are you asking about rules? |
Yeah, custom rules (aren't they usually shipped as plugins in ESLint?). |
Right, but here we dont have to worry about that aspect as we directly tell eslint to load a rule by giving it a name and the object. |
@gyandeeps I see, so we can't just swap them... |
I think so... Maybe in some cases the inner workings of the rules might break based on certain other functionality changes.. |
I think it would make sense to only expose the latest version in the frontend but be able to build/serve older versions as needed. The work that I started in #197 would allow us to do that. In 95c53e5 I added the ability to hide parsers/tools from the menu which is what we can do for the different eslint versions for now. |
Looking at the changes to the lock file (https://gist.github.com/fkling/26a3ad59b43eab66a2065883bb8bfa83) it seems there are a couple of dependencies added (and therefore probably bundled) that are CLI related and therefore not necessary? Might be worth updating edit: Or I guess they are not bundled because you are only importing a subset of eslint... I will go ahead and merge this. We can always optimize later if necessary. |
Actually this breaks production build (reminds me the reason I wanted to use it for Travis in #243, cc @josephfrazier):
|
@fkling Hmm, but you pushed the new website - did this error occur during build for you too? |
Actually, the reason is deeper - |
sorry about this. I had no idea about all this. I would have done something if I had known about these issues. Thanks @RReverser 💯 |
@gyandeeps No, that's okay, just something that needs to be detected and fixed on our side better. |
Ah, I guess we should switch that over. |
Fixes a production build error introduced by #241.
Fixed in dcdcae5 |
@josephfrazier @fkling I've added two different |
Uh I fixed that locally but I guess I forgot to push my changes. Sorry about that 😞 |
You'll probably want to use |
@josephfrazier Ah yeah makes sense... |
@josephfrazier Thanks for the tip, trying: https://travis-ci.org/fkling/astexplorer/builds/245440814 |
Sure thing @RReverser, glad to see it's working now (with a README badge, too)! |
Fixes a production build error introduced by fkling/astexplorer#241.
Fixes a production build error introduced by fkling/astexplorer#241.
Question: