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.

Sign up for GitHub

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

Jump to bottom

Configure publish directory #59

Closed
ekabolotina opened this issue Aug 10, 2022 · 1 comment · Fixed by #84
Closed

Configure publish directory #59

ekabolotina opened this issue Aug 10, 2022 · 1 comment · Fixed by #84
Labels
enhancement New feature or request

Comments

@ekabolotina
Copy link

The signature of npm publish command allows to define the folder used as root:

npm publish [<tarball>|<folder>] [--tag <tag>] [--access <public|restricted>] [--dry-run]

Is it possible to configure <folder> parameter when using JS-DevTools/npm-publish action?
@mcous mcous mentioned this issue Apr 7, 2023
Closed
@mcous mcous added the enhancement New feature or request label Apr 7, 2023
This was referenced Apr 7, 2023
Closed
Closed
@razor-x
Copy link
Collaborator

razor-x commented Apr 14, 2023

Should be handled with the proposal in this issue: #81

@mcous mcous mentioned this issue Apr 14, 2023
Merged
mcous added a commit that referenced this issue Apr 20, 2023
@mcous
Rewrite internals for v2 release (#83)
c5f37b9 
Addresses #15, #35, #36, #47, #51, and #59
@mcous mcous mentioned this issue Apr 20, 2023
Merged
@mcous mcous closed this as completed in #84 Apr 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update to version 2 JS-DevTools/npm-publish
Add target option rxfork/npm-publish
3 participants
@razor-x @mcous @ekabolotina