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

Isaacs/publish non directories #2074

Closed
wants to merge 3 commits into from
Closed

Conversation

isaacs
Copy link
Contributor

@isaacs isaacs commented Oct 28, 2020

Based on #2066, land that first

Depends on npm/libnpmpublish#16, land that and publish before landing this patch. Swap TEMP: commit for one that upgrades to the new semver-major version of libnpmpublish.

Support publishing any kind of spec, not just directories. Also removes the double-pack that we were doing (which isn't horrible, but is a bit less efficient than it could be, of course.)

Improved tests to properly throw when the publish() command raises an error, and ensure that it gets all the way to the callback each time.

This adds a flatOptions.flatten() method, which takes an object full of
config keys, and turns it into an options object.  This method expects
an object that already inherits from npm's defaults, and is thus
expected to be internal only.

This commit also removes some config keys which were used by npm
dependencies at the start of the v7 beta process, but are no longer:

- all lockfile configs (since we don't use lockfiles any more! for
  anything! and good riddance, they're a rats' nest of race conditions)
- cacheMax/cacheMin (we only use preferOffline/offline/online now, so
  these are strictly legacy support as input and never shared with deps)

Once this lands in cli, we can remove the publishConfig handling logic
in npm-registry-fetch, as it will be redundant.
@isaacs isaacs requested a review from a team as a code owner October 28, 2020 23:30
@darcyclarke darcyclarke added Release 7.x work is associated with a specific npm 7 release release: next These items should be addressed in the next release labels Oct 29, 2020
Copy link
Contributor

@nlf nlf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 looks good!

@darcyclarke darcyclarke added release: next These items should be addressed in the next release and removed release: next These items should be addressed in the next release labels Oct 30, 2020
darcyclarke pushed a commit that referenced this pull request Nov 3, 2020
darcyclarke pushed a commit that referenced this pull request Nov 3, 2020
@isaacs isaacs mentioned this pull request Nov 3, 2020
@isaacs isaacs closed this in a1f9be8 Nov 3, 2020
@nlf nlf deleted the isaacs/publish-non-directories branch March 28, 2022 16:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release: next These items should be addressed in the next release Release 7.x work is associated with a specific npm 7 release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants