Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[pull] latest from npm:latest #9

Open
wants to merge 1,029 commits into
base: latest
Choose a base branch
from
Open

[pull] latest from npm:latest #9

wants to merge 1,029 commits into from

Conversation

pull[bot]
Copy link

@pull pull bot commented Feb 2, 2023

See Commits and Changes for more details.


Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

Copy link

codeautopilot bot commented Nov 29, 2023

Your organization has reached the subscribed usage limit. You can upgrade your plan at https://www.codeautopilot.com/#pricing

Disclaimer: This comment was entirely generated using AI. Be aware that the information provided may be incorrect.

Current plan usage: 219.29%

Have feedback or need help?
Discord
Documentation
[email protected]

wraithgar and others added 26 commits May 20, 2024 10:55
This will fix the `npm cache add` to cache package with same header as
it's used in `npm install` by adding extra manifest call with
`fullMetadata: true` while caching to match behaviour with install
command which internally request manifest with fullMetadata.

## References
Closes #7465
<!-- What / Why -->
<!-- Describe the request in detail. What it does and why it's being
changed. -->
Updates `publish` command docs:
 - Refers to `npm tag` which is now `npm dist-tag`
 - Add docs specific for `npm publish --tag`

## References
<!-- Examples:
  Related to #0
  Depends on #0
  Blocked by #0
  Fixes #0
  Closes #0
-->
`npm publish --workspaces` will skip workspace packages marked as
private in package.json.
Currently it's skipping those packages only when you have configured
auth for those packages, it would error out with `ENEEDAUTH` if it
doesn't find the valid auth information.

this fix checks for the private property before checking for auth for
the packages that will essentially not going to get published.

Fixes #7199
Invalid scripts warnings are gone that should not be there
wraithgar and others added 30 commits December 12, 2024 08:52
When searching for multiple terms in npm, the highlighting code has a
bug where it duplicates the output any time there are matching terms.
This fixes the highlighting code.


Before:
![output of "npm search gar promisify" showing the name being
duplicated](https://github.com/user-attachments/assets/2f34ece7-7563-4db1-a540-3bb661a4c3e0)



After:
![output of "node . search gar promisify" showing the name being
displayed
correctly](https://github.com/user-attachments/assets/ba31fcd9-caf3-4a08-8bbb-7f5242f0098b)
Certain project dependency trees may result in an SBOM with duplicate
entries. This fix ensures that each unique dependency (identified by the
combination of package name and version) only appears in the SBOM once.
Applies to both SPDX and CycloneDX SBOM formats.

Specific to the CycloneDX format, this change also removes the
`cdx:npm:package:path` property from the `component` entries in the
generated SBOM. Since the same package may be present at multiple paths
within the project and we're now de-duplicating those packages, it no
longer makes sense to include this in the SBOM. This does not impact the
SPDX format as there is no equivalent property.

Fixes: #6967

Signed-off-by: Brian DeHamer <[email protected]>
Noticed some of the resources pointed to external sites not controlled
by npm or github and wanted to clean them up so they can't be squatted
on.
Setting `tag` in `publishConfig` constitutes a "non default" scenario.
documentation of `ls` command specifies that `depth` flag if not set
defaults to `1` but as per code it uses 0 as default value.
https://github.com/npm/cli/blob/dc31c1bdc6658ab69554adcf2988ee99a615c409/lib/commands/ls.js#L113-L116

fixes: #7979
This PR fixes small typos in the documentation for "configuring
npm/package-json"
…8054)

Merges #7993 /
#7994 /
#7995

- [x] adds ability to --force publish without latest check
- [x] adds ability to --force publish of prerelease without tag
- [x] consider equality in publish dist tag check error message
Update the copy for "requirements" to specify that it is the Node.js
support lifecycle that is key, not a specific version.

Also removed the badges from the readme. Most of that info is already on
the page as parsed by GitHub.
#8054 broke the smoke test because were
publishing the current version in a test
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.