Skip to content
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

gatsby 2.30.0 to 2.31.0 breaks .eslintrc.js #29133

Closed
theskillwithin opened this issue Jan 21, 2021 · 4 comments · Fixed by #29317
Closed

gatsby 2.30.0 to 2.31.0 breaks .eslintrc.js #29133

theskillwithin opened this issue Jan 21, 2021 · 4 comments · Fixed by #29317
Labels
status: confirmed Issue with steps to reproduce the bug that’s been verified by at least one reviewer. type: bug An issue or pull request relating to a bug in Gatsby

Comments

@theskillwithin
Copy link
Contributor

Description

5f0d214

Steps to reproduce

Upgrade to gatsby 2.31.1 from 2.31.0 and .eslintrc.js file is ignored

  System:
    OS: macOS 11.1
    CPU: (12) x64 Intel(R) Xeon(R) CPU E5-1650 v2 @ 3.50GHz
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 14.15.3 - ~/.nvm/versions/node/v14.15.3/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 6.14.11 - ~/.nvm/versions/node/v14.15.3/bin/npm
  Languages:
    Python: 2.7.17 - /usr/local/bin/python
  Browsers:
    Chrome: 88.0.4324.96
    Firefox: 84.0
    Safari: 14.0.2
  npmPackages:
    gatsby: ^2.31.1 => 2.31.1
    gatsby-image: ^2.10.0 => 2.10.0
    gatsby-plugin-canonical-urls: ^2.9.0 => 2.9.0
    gatsby-plugin-disqus: ^1.2.2 => 1.2.2
    gatsby-plugin-google-tagmanager: ^2.10.0 => 2.10.0
    gatsby-plugin-local-search: ^2.0.0 => 2.0.0
    gatsby-plugin-manifest: ^2.11.0 => 2.11.0
    gatsby-plugin-offline: ^3.9.0 => 3.9.0
    gatsby-plugin-postcss: ^3.6.0 => 3.6.0
    gatsby-plugin-react-helmet: ^3.9.0 => 3.9.0
    gatsby-plugin-robots-txt: ^1.5.5 => 1.5.5
    gatsby-plugin-s3: ^0.3.8 => 0.3.8
    gatsby-plugin-sass: ^3.1.0 => 3.1.0
    gatsby-plugin-sharp: ^2.13.1 => 2.13.1
    gatsby-plugin-sitemap: ^2.11.0 => 2.11.0
    gatsby-plugin-svgr: ^2.1.0 => 2.1.0
    gatsby-plugin-webpack-bundle-analyser-v2: ^1.1.18 => 1.1.18
    gatsby-source-contentful: ^3.1.3 => 3.1.3
    gatsby-source-filesystem: ^2.10.0 => 2.10.0
    gatsby-transformer-remark: ^2.15.0 => 2.15.0
    gatsby-transformer-sharp: ^2.11.0 => 2.11.0
@theskillwithin theskillwithin added the type: bug An issue or pull request relating to a bug in Gatsby label Jan 21, 2021
@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Jan 21, 2021
@hendra-go
Copy link
Contributor

Confirmed. I also experience the same issue.

@LekoArts LekoArts added status: confirmed Issue with steps to reproduce the bug that’s been verified by at least one reviewer. and removed status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer labels Jan 22, 2021
@mikaelkristiansson
Copy link
Contributor

Same here

kremalicious added a commit to oceanprotocol/docs that referenced this issue Jan 26, 2021
* everything higher prevents `npm start` from succeeding
* needs resolve from gatsby gatsbyjs/gatsby#29133
@LekoArts LekoArts changed the title gatsby 2.31.0 to 2.31.0 breaks .eslintrc.js gatsby 2.30.0 to 2.31.0 breaks .eslintrc.js Jan 27, 2021
@jablonski
Copy link

Same issue here, prevents us from updating to 2.31.x

@vladar
Copy link
Contributor

vladar commented Feb 4, 2021

Fixed in gatsby@2.32.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: confirmed Issue with steps to reproduce the bug that’s been verified by at least one reviewer. type: bug An issue or pull request relating to a bug in Gatsby
Projects
None yet
6 participants