Skip to content

Support ESLint 8.x #2890

Closed

Description

ESLint v8.0.0 is released 🎉

It would be awesome to have official ESLint 8 support. 👊
I'm happy to help where I can of course 🙂

Activity

  1. iclanton commented on Sep 7, 2021

    @iclanton
    Member

    Pete Gonzalez (@octogonz) - want to take a look at this?

  2. octogonz commented on Sep 10, 2021

    @octogonz
    Collaborator

    We don't normally adopt or support beta versions of tools (since it's already a nontrivial time investment to keep up with officially released versions 😇).

    I'm fine however if someone wants to make a PR that enables usage of eslint-v8.0.0-beta-*. Heft should probably print a notice to the console saying it's not officially supported.

    I'm also curious to see what will happen with @rushstack/eslint-patch.

  3. added
    enhancementThe issue is asking for a new feature or design change
    help wantedIf you're looking to contribute, this issue is a good place to start!
    on Sep 10, 2021
  4. changed the title [-][eslint-config] Support ESLint 8.x[/-] [+]Support ESLint 8.x[/+] on Sep 10, 2021
  5. lukashass commented on Oct 10, 2021

    @lukashass
    Contributor

    ESLint 8.0.0 was just released 😉 https://eslint.org/blog/2021/10/eslint-v8.0.0-released

  6. anonrig commented on Oct 12, 2021

    @anonrig

    Any updates or news from this issue?

  7. marcoreni commented on Oct 26, 2021

    @marcoreni

    Ian Clanton-Thuon (@iclanton) I think this should be reopened since #2965 only solved issues for eslint-patch package.

  8. D4N14L commented on Nov 29, 2021

    @D4N14L
    Contributor

    Marco Reni (@marcoreni) is correct, this should be re-opened. I will take a look at this soon.

  9. lukashass commented on Nov 30, 2021

    @lukashass
    Contributor

    Daniel (@D4N14L) FYI I already started this in #3009. Not sure if that covers everything needed to close this issue. Also, it is blocked by upstream changes as far as I can tell, but feel free to continue.

  10. D4N14L commented on Dec 1, 2021

    @D4N14L
    Contributor

    Lukas (@lukashass) yes, I noticed this just recently, sorry for missing that! I already had some additional changes in my branch, so I'll likely create a separate PR for it. I'll tag you when I get that out.

  11. stefaneg commented on Jan 24, 2022

    @stefaneg

    I am working on getting eslint to work with heft, having trouble making it work with eslint 8.7.0.

    Is it possible that the documentation is out of date here?

    https://www.npmjs.com/package/@rushstack/eslint-config

  12. D4N14L commented on Jan 24, 2022

    @D4N14L
    Contributor

    Guðlaugur Stefán Egilsson (@stefaneg) it seems like it works successfully (see this PR: #3185). What is the issue you're having?

  13. stefaneg commented on Jan 24, 2022

    @stefaneg

    The error I get is this when execute heft build with .eslintrc.js exactly as it specified in the documentation. I have verified that everything is present in node_modules at the correct paths.

    > heft build 
    Project build folder is "/Users/gulli/src/github.com/rush-example/libraries/logging"
    Starting build
     ---- Pre-compile started ----
     ---- Pre-compile finished (1ms) ----
     ---- Compile started ----
    [typescript] Using TypeScript version 3.9.10
    [eslint] Using ESLint version 8.7.0
     ---- Compile encountered an error (2239ms) ----
    -------------------- Finished (2.51s) --------------------
    Project: @tm.is/logging@3.6.10
    Heft version: 0.44.2
    Node version: v16.13.1
    Error: Cannot read config file: /Users/gulli/src/github.com/rush-example/libraries/logging/.eslintrc.js
    Error: Failed to patch ESLint because the calling module was not recognized
    

    I tried downgrading ESLint to 7.32.0, and the error persists, so the issue seems to be something else.

  14. stefaneg commented on Jan 24, 2022

    @stefaneg

    It looks like the message is originating here:

    'Failed to patch ESLint because the calling module was not recognized.\n' +

    Hard to be sure unless there is an output processor that outputs only the first line of the exception message to stderr.

    EDIT:

    Turned out that I managed somehow to install an old version of @rushstack/eslint-config which led to those obscure errors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementThe issue is asking for a new feature or design changehelp wantedIf you're looking to contribute, this issue is a good place to start!

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions