IQSS / IQSS/dataverse-frontend
Create test registry for the @iqss/dataverse-design-system package
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 31
- Forks
- 26
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 4
Description
Overview of the Feature Request
We need to create a test registry for the @iqss/dataverse-design-system npm module.
This way we can test the publishing of the package without actually publishing a new version to the npm registry.
Some options:
-
localhost registry using verdaccio
What kind of user is the feature intended for?
@iqss/dataverse-design-system developers
What inspired the request
- #116
We had to publish a patch for the 1.0.0 because the local test publishing as recommended by npm didn't raise a bug that later on occurred when actually publishing the package
What existing behavior do you want changed?
None
Any brand new behavior do you want to add to Dataverse?
Create a test registry for the design system package
Any open or closed issues related to this feature request?
- #81
- #23
- #116
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 how the @iqss/dataverse-design-system package is built and published, then read related issues #116, #81, and #23. Compare the proposed Verdaccio and GitHub npm registry approaches for this repository. Done means developers can publish and consume a test package without publishing a new version to the public npm registry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100