npm token documentation is wrong #123681
Replies: 1 comment
-
i guess we're still using legacy tokens? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm trying to create a publish/automation token. The docs (https://docs.npmjs.com/creating-and-viewing-access-tokens) have a step 4 that does not exist on the token generation flow on npm.
docs:
![image](https://private-user-images.githubusercontent.com/119972/330200605-c20dda4c-1cbf-42d1-8adc-0ce4bc022028.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTg4MjI3MTQsIm5iZiI6MTcxODgyMjQxNCwicGF0aCI6Ii8xMTk5NzIvMzMwMjAwNjA1LWMyMGRkYTRjLTFjYmYtNDJkMS04YWRjLTBjZTRiYzAyMjAyOC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNjE5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDYxOVQxODQwMTRaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0wN2Q0MWNmYTlmMjk2ZmQ2OWMwODk5YjFhMzhjZDk5MDhlNTdhNmM3YWE3MDcxZjA1Y2M3ZjM0ZjY0MmE1NWFjJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.WjEAUIgNOd3L7GW-MQwXsgd9YhMo-A8jU0W5Dnt9XNk)
Nowhere during the creation token process do I get to choose a type. It asks for token name, description, expiration, ip-ranges, packages/scopes, organizations. Nowhere to select the type as documented.
Beta Was this translation helpful? Give feedback.
All reactions