KhronosGroup / KhronosGroup/glTF-Validator
Add compatibility with npm 2FA
- Dominant language
- Dart
- Stars
- 470
- Forks
- 77
- PR merge metrics
- No merged PRs in 30d
Description
I enabled 2FA on my npm account some weeks ago, I guess we haven't published the validator since then. Looks like we need to add a publish pre-step that asks for the OTP code and passes it on the command line with `--otp=` (without the angle brackets). Note that this should be done just prior to the publish step, as the codes only last 60 seconds at most, and entering the code takes some of that time, so we wouldn't want `npm install` or other pre-process steps in between the code entry and the publish command.
```
npm ERR! publish Failed PUT 401
npm ERR! code E401
npm ERR! This operation requires a one-time password from your authenticator.
npm ERR! You can provide a one-time password by passing --otp= to the command you ran.
npm ERR! If you already provided a one-time password then it is likely that you either typoed
npm ERR! it, or it timed out. Please try again.
```
In the meantime I've published `2.0.0-dev.2.5` by halting the script at this point and manually publishing.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the repository's publish script and the existing publish step. Add an OTP prompt immediately before publishing, pass the entered value as --otp=, and ensure no install or other preprocessing occurs between prompt and publish; verify the release flow uses the code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100