openedx / openedx/frontend-build
`jest.config.js` should search for both `.js` and `.jsx` extensions for `env.config`
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 25
- Forks
- 41
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 5
Description
In the likelihood that we'll need to be able to use env.config.jsx whenever a function is imported into the JS config, Jest will need to be able to handle it here.
For the sake of making sure bases are covered, Webpack's common config already handles both extensions.
Contributor guide
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
Open config/jest.config.js at the linked line and compare its env.config extension handling with config/webpack.common.config.js. Update the Jest configuration so both .js and .jsx are covered, then verify that env.config.jsx can be resolved when imported by the JavaScript config.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100