)
        err.code = 'EUNSUPPORTED'
        throw err
      }
    }
    var npxArgs = [process.argv0, '[fake arg]', '--always-spawn', packageName, ...process.argv.slice(4)]
    var parsed = npx.parseArgs(npxArgs, NPM_PATH)

    return npx(parsed)
      .then(() =&gt; cb())
      .catch(cb)
  }
  var dir = process.cwd()
  log.pause()
  var initFile = npm.config.get('init-module')
  if (!initJson.yes(npm.config)) {
    output([
      'This utility will walk you through creating a package.json file.',
      'It only covers the most common items, and tries to guess sensible defaults.',
      '',
      'See `npm help json` for definitive documentation on these fields',
      'and exactly what they do.',
      '',
      'Use `npm install ` afterwards to install a package and',
      'save it as a dependency in the package.json file.',
      '',
      'Press ^C at any time to quit.'
    ].join('\n'))
  }
  initJson(dir, initFile, npm.config, noProgressTillDone(function (er, data) {
    log.resume()
    log.silly('package data', data)

Most popular functions for init-package-json

To help you get started, we’ve selected a few init-package-json examples, based on popular ways it is used in public projects.

init-package-json

init-package-json.yes