patternfly / patternfly/patternfly-react
Spike - npm package.json exports paths
Open
Nobody has claimed this yet.
PF Team
Stale
- Dominant language
- TypeScript
- Stars
- 862
- Forks
- 392
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 9
Description
Investigate a more intentional and cleaner exports structure, which would go into a breaking change release. This would be an allow-list of import paths, opposed to the whole package being able to be imported from any path.
Jira Issue: PF-2562
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
Start by reviewing the package.json exports configuration and the current import paths described in the issue. Define the intended allow-list for a breaking-change release and document which paths remain supported; the issue does not name tests or other files to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100