keyz / keyz/identity-obj-proxy
Support named exports
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 507
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
When using CSS modules with named exports (e.g. you're using Typescript and typings-for-css-modules-loader), they look like:
export const foo = 'foo';
export const barBaz = 'barBaz';
And the consumer uses as:
import * as styles from './styles.css';
...
<div className={styles.barBaz} />
This mock does not play nice. I've found that returning true for the __esModule check here does work - essentially saying that our mocked module is an ES module and the keys are the named exports.
Any ideas if and how this project could accommodate that? E.g. using identity-obj-proxy/esm?
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 in src/index.js at the __esModule check linked in the issue, then compare its current behavior with the named-export examples. Verify the chosen approach using import * as styles and confirm that named CSS keys such as barBaz are available through the mock without breaking existing CSS-module behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100