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

[FEATURE] Use validate-npm-package-name to validate package names #54

Open
iarna opened this issue Nov 17, 2014 · 3 comments
Open

[FEATURE] Use validate-npm-package-name to validate package names #54

iarna opened this issue Nov 17, 2014 · 3 comments
Labels
feature

Comments

@iarna
Copy link
Contributor

iarna commented Nov 17, 2014

Let's get this logic centralized. This'd replace ensureValidName. Things that use fixNameField to validate names should probably be updated to use validate-npm-package-name directly too. cough npm-registry-client cough
@othiym23
Copy link
Contributor

We should definitely do this!

cough npm-registry-client cough

📝 an issue plzthxomgbbq!

@iarna
Copy link
Contributor Author

iarna commented Nov 17, 2014

I'd like to see npm/validate-npm-package-name#1 addressed before we do the npm-registry-client changes, as I'd prefer to not change its semantics.

@zeke
Copy link
Contributor

zeke commented Nov 18, 2014

An attempt is here: npm/validate-npm-package-name#2

@settings settings bot removed the enhancement label Aug 18, 2021
@darcyclarke darcyclarke changed the title Use validate-npm-package-name to validate package names [FEATURE] Use validate-npm-package-name to validate package names Jul 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@zeke @othiym23 @darcyclarke @iarna