-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Fix eslint #6317
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
Fix eslint #6317
Conversation
pinning the node version worked! :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes look good to me.
I don't have a strong opinion here because I don't have too much experience.
It seems the current LTS version is v12.x
. Was that the problem? Why it does not build with the latest LTS version?
That's the problem the linter is given, guess they updated the lts version. |
yup, they updated the LTS version from v10 to v12 https://nodejs.org/en/download/releases/ a couple of days ago |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change looks good! I don't think we should have JS changes added here though. What changed here to generate new JS?
Nothing I guess, just built them to make sure we have the latest files. |
@agjohnson js files are omited now |
There is something that happens here, and it's hard to tell if anything even changed in the built assets. In my environment, I always generate new assets, different from everyone else. I had to have David do the build steps on last release because my environment was re-creating all the assets -- his didn't recreate anything 😕 |
I just rebuilt the js assets.