Add cache clearing info to JS Build config docs#3297
Conversation
Signed-off-by: s-stumbo <sally.stumbo@chainguard.dev>
✅ Deploy Preview for ornate-narwhal-088216 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Signed-off-by: s-stumbo <sally.stumbo@chainguard.dev>
Signed-off-by: s-stumbo <sally.stumbo@chainguard.dev>
indexzero
left a comment
indexzero
left a comment
There was a problem hiding this comment.
lgtm 👍 net-net positive change that can be merged as-is. Called out some spots we could consider for future improvements
| //libraries.cgr.dev/javascript/:_auth="$token" | ||
| //libraries.cgr.dev/javascript/:always-auth=true |
There was a problem hiding this comment.
When Universal Repository is enabled this would aldo need to include:
//libraries.cgr.dev/javascript-upstream/:_auth="$token"
//libraries.cgr.dev/javascript-upstream/:always-auth=true
There was a problem hiding this comment.
@indexzero just checking this is specific to yarn classic?
| Then, set auth and set the registry URL to point to Chainguard in your user `.npmrc` file: | ||
|
|
||
| ```bash | ||
| cat > .npmrc << 'EOF' |
There was a problem hiding this comment.
This is non-blocking food for thought but: almost all package managers respect .npmrc. It may be less confusing / easier to follow if we unify documentation about .npmrc under a section dedicated to that particular file.
fritzy
left a comment
fritzy
left a comment
There was a problem hiding this comment.
pnpm v10 includes pnpm cache delete
pnpm also has a separate cache dir
rm -rf ${XDG_CACHE_HOME:-$HOME/.cache}/pnpm
and with pnpm you may need to delete your node_modules.
This may still not be enough. We have customers really struggling with this.
Signed-off-by: s-stumbo <sally.stumbo@chainguard.dev>
Signed-off-by: s-stumbo <sally.stumbo@chainguard.dev>
Signed-off-by: s-stumbo <sally.stumbo@chainguard.dev>
5 participants
[ ] Check if this is a typo or other quick fix and ignore the rest :)
Type of change
Update to JS build config docs
What should this PR do?
Adds info about clearing the caches, from Angela's draft: https://docs.google.com/document/d/13kMq9F1mUooOoLsIXN_EuAs51J8TLshw4D0-uZTK7p0/edit?tab=t.0#heading=h.pqhjvgw1gl4l
Why are we making this change?
Reduce friction in the user experience
What are the acceptance criteria?
Content should be clear and accurate and appear in expected location
How should this PR be tested?
Review deploy preview