less/less.js

Can't use package.json property `imports` to import subpath module.

Open

#3715 opened on Apr 20, 2022

View on GitHub
 (5 comments) (0 reactions) (0 assignees)JavaScript (16,977 stars) (3,517 forks)batch import
bugfeature requestgood first issueup-for-grabs

Description

My package.json :

{
    ...,
    "imports": {
        "#style/*": "./src/style/*"
    }
    ...
}

when i use less-loader to load less file like:

@import (refrence) "#style/mixins"

i got error like:

'#style/mixins' wasn't found. Tried - .less
      Error in D:\Development\xxx\index.module.less (line 2, column 0)

I think less throws an error before using the FileManager to resolve the file, making it impossible to use the webpack resolver to resolve the real path.

When I change the code to the following, everything works fine:

@import (refrence) "~#style/mixins"

My packages version is:

  • less@4.1.2
  • less-loader@10.2.0
  • webpack@5.68.0
  • enhanced-resolve@5.9.2

Contributor guide

Tech stack
javascriptnodejs
Domain
build systemtooling
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Lesswebpackenhanced resolve
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate the Less file resolution logic to see why it fails to recognize package.json 'imports' before using FileManager. Look at the Less source code for how imports are resolved, particularly the import plugin flow. Examine the interaction with less loader and webpack's enhanced resolve. Check if a custom FileManager can override the resolution to support package.json imports. Review any existing comments or related issues for clues about the expected behavior.