npmpackage.info

Gathering detailed insights and metrics for @minar-kotonoha/inquirer-npm-name

@minar-kotonoha/inquirer-npm-name - 3.0.0 | npmpackage.info

@minar-kotonoha/inquirer-npm-name

Helper function using inquirer to validate a value provided in a prompt does not exist as an npm package.

3.0.0

MIT

JavaScript

7.10 kB

1.9

Installations

npm install @minar-kotonoha/inquirer-npm-name

Developer Guide

BETA

Typescript

No

Module System

CommonJS

Node Version

14.5.0

NPM Version

6.14.5 Score

61.3

Supply Chain

91.6

Quality

Maintenance

Vulnerability

98.9

License

Pull Requests

Open

1

Total

28

Closed

16

Merged

11

Issues

Open

2

Total

8

Closed

6

Releases

v3.0.0

Updated on Dec 29, 2017

v2.0.0

Updated on May 08, 2016

v1.0.0

Updated on May 08, 2016

View All 3 releases

Languages

JavaScript

JavaScript (100%)

Developer

SBoudrias

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

MIT License

13 Stars

32 Commits

5 Forks

1 Watchers

106 Branches

4 Contributors

Updated on Jul 28, 2021

Maintainers

View All 4 Contributors

Package Meta Information

Latest Version

3.0.0

Package Id

@minar-kotonoha/inquirer-npm-name@3.0.0

Unpacked Size

7.10 kB

Size

3.00 kB

File Count

NPM Version

6.14.5

Node Version

14.5.0

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

npm-name upper-case-first validate-npm-package-name

Dev Dependencies

eslint eslint-config-xo-space gulp gulp-cli gulp-coveralls gulp-eslint gulp-exclude-gitignore gulp-istanbul gulp-line-ending-corrector gulp-mocha gulp-nsp gulp-plumber mocha pinkie-promise proxyquire sinon

inquirer-npm-name

Helper function using inquirer to validate a value provided in a prompt does not exist as a npm package.

The supplied value must be a valid package name (as per validate-npm-package-name); otherwise, the user will again be prompted to enter a name.

If the value is already used as a npm package, then the users will be prompted and asked if they want to choose another one. If so, we'll recurse through the same validation process until we have a name that is unused on the npm registry. This is a helper to catch naming issue in advance, it is not a validation rule as the user can always decide to continue with the same name.

Install

1$ npm install --save inquirer-npm-name

Usage

1var inquirer = require('inquirer');
2var askName = require('inquirer-npm-name');
3
4askName(
5  {
6    name: 'name',
7    message: 'Some Module Name' // Default: 'Module Name'
8  },
9  inquirer
10).then(function(answer) {
11  console.log(answer.name);
12});
13
14// Equivalent to {name: 'name'}
15askName('name', inquirer).then(function(answer) {
16  console.log(answer.name);
17});

Inside a Yeoman Generator you'd call it this way:

1var generators = require('yeoman-generator');
2var inquirer = require('inquirer');
3var askName = require('inquirer-npm-name');
4
5module.exports = generators.Base.extend({
6  prompting: function() {
7    return askName(
8      {
9        name: 'name',
10        message: 'Module Name'
11      },
12      this
13    ).then(function(name) {
14      console.log(name);
15    });
16  }
17});

askName takes 2 parameters:

prompt an Inquirer prompt configuration or just a string to serve as name.
inquirer or any object with a obj.prompt() method.

Returns: A Promise resolved with the answer object.

License

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

1

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Maintained

Determines if the project is "actively maintained".

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

1.9

/10

Last Scanned on 2025-07-07

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More