Log in to npm when using the release task
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- release
Research direction
Locate the release task and inspect its existing checks for npm login status and publish permissions. Determine how credentials would be passed, how automatic login and logout should work, and define completion around a release that handles authentication without requiring a pre-existing login.
Written by the indexing model from the issue text.
Description
@matt-gadd commented on Fri Sep 02 2016
The task currently checks whether the user is logged in, and that the user has permissions to publish the package. It might be worth adding the capability to pass credentials to the task and it logging in automatically (as well as logging out after the release is completed).
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dojo/scripts
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
dependencies
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
safetrustcr/dApp-SafeTrust#426 ·
-
area:workflow bug ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
fil-donadoni/tolaria#4409 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Fission-AI/OpenSpec#1960 ·
-
Add dependabot Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
corsairdev/corsair#1764 ·