Remove deprecated unsafe-perm setting from .npmrc#8317
Merged
Conversation
Agent-Logs-Url: https://github.com/pubkey/rxdb/sessions/7123ac0f-0423-4cf5-9f21-266c65685331 Co-authored-by: pubkey <8926560+pubkey@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
pubkey
April 9, 2026 13:11
View session
Owner
|
@copilot run "npm run docs:build" and fix it |
Copilot stopped work on behalf of
pubkey due to an error
April 10, 2026 06:13
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Running
npm installornpm run buildproduces the following warning on every invocation:This warning appears repeatedly during the build because each sub-command also triggers it, resulting in many lines of noise in the output.
Fix
Removed the deprecated
unsafe-perm = trueline from.npmrc. This setting is no longer recognized by modern npm versions and has no effect. The remaining.npmrcsettings (package-lock=falseandsave-exact=true) are unaffected.Verification
npm installproduces zero warningsnpm run buildcompletes with zero warningsnpm run lintpassesnpm run check-typespasses