Skip to content

Clarifying: Resolving import at-rules not resolving webpack's resolve.modules? #1064

Open
@chardskarth

Description

Documentation Is:
It's mentioned here that resolution is done:

  1. First, by resolving as a relative path
  2. If not found, it will try to search through the node_modules directory.
  • Missing
  • Needed
  • Confusing
  • Not Sure?

Please Explain in Detail...

I think it should be mentioned that webpack's alias is tried to be resolved before the "node_module" resolution part.

Which brings me to my next question:
Is it expected that webpack's resolve.modules is not used as an alternative for resolution?

Your Proposal for Changes

Indicate, under Webpack provides an [advanced mechanism to resolve files](https://webpack.js.org/concepts/module-resolution/). that specifying a resolution via webpack's resolve alias can be used.

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions