Having issues resolving package
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 738
- Forks
- 48
- PR merge metrics
- No merged PRs in 30d
Description
I'm confused as to why this doesn't work:
```
@import "@material/button/mdc-button";
```
Here is `tree --matchdirs node_modules/@material/button`
```
node_modules/@material/button
├── README.md
├── _mixins.scss
├── _variables.scss
├── dist
│ ├── mdc.button.css
│ └── mdc.button.min.css
├── mdc-button.scss
└── package.json
```
Shouldn't this simply resolve to node_modules/@material/button/mdc-button.scss as written?
I am using broccoli-eyeglass
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the @import "@material/button/mdc-button" case with broccoli-eyeglass and compare it with the node_modules/@material/button tree shown in the report. Read the package-resolution behavior involved and establish whether the import should resolve to mdc-button.scss; done means the resolution behavior is corrected or clearly documented with a verified reproduction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sass
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100