Skip to content

[v5] Replace CaseSensitivePathsPlugin with eslint import/no-unresolved rule #11272

Open
Open
[v5] Replace CaseSensitivePathsPlugin with eslint import/no-unresolved rule#11272
Labels
issue: proposalneeds triage
Milestone
5.x

Description

@raix
raix
opened on Aug 2, 2021

Is your proposal related to a problem?

The CaseSensitivePathsPlugin is expensive, would be better for performance to use eslint rule https://github.com/import-js/eslint-plugin-import/blob/master/docs/rules/no-unresolved.md#casesensitive

referece: #11201 (comment)

Describe the solution you'd like

a2c859a

Describe alternatives you've considered

Additional context

#11201 (review)

Activity

  1. raix
    added
    issue: proposal
    needs triage
    on Aug 2, 2021
  2. raix
    added this to the 5.0 milestone on Aug 2, 2021

  3. dantman commented on Nov 5, 2021

    @dantman
    dantman
    on Nov 5, 2021

    This issue is part of the 5.0 milestone, suggesting it's blocking the release of CRA v5.

    However investigating it it looks like CRA v4 also uses CaseSensitivePathsPlugin. So this is not a regression in the v5 alpha that needs fixing but a feature request.

    If this isn't being worked on soon. Could this be moved to 5.x (or 6.0 if it's breaking)?

  4. raix
    modified the milestones: 5.0, 5.x on Nov 6, 2021
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

    issue: proposalneeds triage

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions