Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Gauging Interest in Guide for Verdaccio Private Registry Uplink
See original GitHub issueI am writing to gauge interest in whether or not create-react-app would like a new User Guide detailing how to run end to end testing with a private verdaccio uplink, enabling the installation of private packages as dependencies.
Context
create-react-app uses verdaccio to spin up a local registry to publish and pull the current changeset being built - effectively testing exactly how the user would. (By the way, this is awesome!)
create-react-app has the luxury of using the default verdaccio config which includes the public npm registry. All packages to be installed are public.
Problem
A problem is encountered if a team wishes to fork create-react-app and add private or proxied npm packages, as they won’t be found on the public registry (at least unauthenticated). This causes yarn installs to fail with 404s during CI. I think one could argue this may be a pretty specific problem, depending on if teams choose to fork the whole monorepo or just react-scripts, but we’ve found value in the former, and as such, am writing this issue to propose the solution.
Solution
What we’ve down to support this behavior is
- add our private registry as an uplink
- alter end to end scripts to add
authorheaderproperties to the verdaccio confg file during CI, being careful not to leak any secret.
This allows us to test generation of create-react-app while pulling down our custom/private packages.
We find it unlikely that we are the only team to encounter this use case. Would create-react-app accept a PR to the User Guide detailing how to accomplish this task?
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I’m not saying it doesn’t belong in the user guide, just that I’m not sure.
Here’s a proposal: submit a PR adding a section to the user guide (maybe something like “CI testing with private packages”). If it’s general enough and useful to others, we’ll merge it. If not you can move it to a blog post and we’ll just link to the blog post from the user guide.
Sure, we can add this somewhere. Send a PR?