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
SyntaxError: Invalid regular expression flags From 6.6.0 Release #12493
Comments
That's the According to this compat-table it should be supported in Node >= 8.10 |
Our Node v8.16.2 build is passing, @emilyrohrbough on which Node version is your build failing? |
On node v8.9.4 its failing |
The latest major release line of ESLint currently supports the following engines: {
"node": "^8.10.0 || ^10.13.0 || >=11.10.1"
} |
Can we just make a change to not require this flag? The s flag just means dots represent newlines, right? Could we use something like |
Node: v8.6.0 Same error:
|
Yes, ESLint supports only Node.js You should see the following warning if you installed ESLint with old Node.js:
See also Migrating to v6.0.0. |
@mdjermanovic & @mysticatea it looks like I am on node 8.9.2 and missed the 8.10 minimum requirement for the upgrade. whoops!! I did just verify my build, and I am not seeing the warning messages in install for the non-supported engines/node verisons: Log Output:➜ chart-summary-component git:(add-menu-sass-side) run clean:install
> chart-summary-component@0.0.0 clean:install /Users/er047227/orion/chart-summary/chart-summary-component
> npm run clean && npm install
> chart-summary-component@0.0.0 clean /Users/er047227/orion/chart-summary/chart-summary-component
> rm -f ./package-lock.json && rm -rf node_modules
npm WARN deprecated left-pad@1.3.0: use String.prototype.padStart()
> fsevents@1.2.9 install /Users/er047227/orion/chart-summary/chart-summary-component/node_modules/fsevents
> node install
node-pre-gyp WARN Using request for node-pre-gyp https download
[fsevents] Success: "/Users/er047227/orion/chart-summary/chart-summary-component/node_modules/fsevents/lib/binding/Release/node-v57-darwin-x64/fse.node" is installed via remote
> chart-summary-component@0.0.0 prepare /Users/er047227/orion/chart-summary/chart-summary-component
> npm run build
> chart-summary-component@0.0.0 build /Users/er047227/orion/chart-summary/chart-summary-component
> npm run compile
> chart-summary-component@0.0.0 compile /Users/er047227/orion/chart-summary/chart-summary-component
> npm run compile:clean && npm run compile:build
> chart-summary-component@0.0.0 compile:clean /Users/er047227/orion/chart-summary/chart-summary-component
> rm -rf lib
> chart-summary-component@0.0.0 compile:build /Users/er047227/orion/chart-summary/chart-summary-component
> babel src --out-dir lib --copy-files
Successfully compiled 17 files with Babel.
npm WARN eslint-config-airbnb@18.0.1 requires a peer of eslint-plugin-react-hooks@^1.7.0 but none is installed. You must install peer dependencies yourself.
added 779 packages in 22.343s |
newer version of eslint uses a regular expression flag which are only supported by node >= 8.10 from instrospection, atom came with node v8.9.3, hence it can't use the latest version of eslint breaking linter-eslint extension ref: - eslint/eslint#12493
I get the same output error. Tested with node 8.16.0 and 10.15.3. If i refactor |
Version 8.9.0 on Udacity workspace fails during npm start. See eslint/eslint#12493
Updates all the devDependencies except for eslint. eslint requires node >=8.10 but on AppVeyor emscripten overrides the node.js version with 8.9.1. eslint/eslint#12493 ni#658
Updates all the devDependencies except for eslint. eslint requires node >=8.10 but on AppVeyor emscripten overrides the node.js version with 8.9.1. eslint/eslint#12493 #658
Tell us about your environment
What parser (default, Babel-ESLint, etc.) are you using?
default
Please show your full configuration:
Configuration
My eslint-config extends: https://github.com/cerner/eslint-config-terra/blob/master/eslint.config.js
What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.
The latest eslitn version was pulled in during a CI build and failed lint tests.
I was able to reproduce by removing my node_modules dir locally and running install again. Running eslitn resulting in errors.
What actually happened? Please include the actual, raw output from ESLint.
This recent change is causing builds to fail with the following error:
The text was updated successfully, but these errors were encountered: