CLI tool for running Yeoman generators

Overview

yo npm Build Status Coverage Status Gitter OpenCollective

What's Yeoman?

Yeoman helps you to kickstart new projects, prescribing best practices and tools to help you stay productive.

To do so, we provide a generator ecosystem. A generator is basically a plugin that can be run with the yo command to scaffold complete projects or useful parts.

Usage

# install yo
npm install --global yo

# install a generator
npm install --global generator-webapp

# run it
yo webapp

To create and distribute your own generator, refer to our official documentation

You can also run a local generator on your computer as such:

# Running a local generator
yo ./path/to/local/generator

Options

  • --no-color - Disable colors.
  • --version - Print the current yo version.
  • --help - Print yo help menu with the list of found generators.
  • --[no-]insight - Toggle anonymous Insight tracking which helps us improve Yeoman. Using either of these flags on the first run will prevent you from being prompted about it interactively. The flags can also be used to change it later on.
  • --generators - Print available generators.
  • --local-only - Disable lookup of globally-installed generators.

Troubleshooting

Running yo doctor command can help you troubleshoot common issues.

If doctor doesn't help, then check opened issues for a similar problem. Open a new issue if your problem haven't been reported yet. Make sure to always include the version of yo (yo --version) and Node.js (node --version) you use.

If your issue only occurs using a generator, please report the issues on the generator's repository.

Contribute

See the contributing docs.

Changelog

See the release page.

Backers

Love Yeoman work and community? Help us keep it alive by donating funds to cover project expenses!
[Become a backer]

License

BSD-2-Clause © Google

Comments
  • Allow running as root using explicit parameter

    Allow running as root using explicit parameter

    Most time i am using Docker for quick tests of new software. For the sake of convinience i just install and run everything there as root and throw away the container later.

    It would be nice if yo could allow beeing executed as root like bower does.

    opened by webwurst 47
  • 🐛 yo version check fails while behind proxy

    🐛 yo version check fails while behind proxy

    Type of issue

    🐛 bug


    My environment

    • OS version/details: Windows 10 64-bit
    • Node version: 10.5.0
    • npm version: 6.1.0
    • Version of yo : 2.0.3

    Expected behavior

    I expect the version check to use the same proxy settings as npm does.

    Current behavior

    At work I'm sitting behind a company proxy and for some reason the version check fails while the install succeeds.

    Command line output

    PS C:\Users\xxqqvc\Projects\test> npm init -y
    PS C:\Users\xxqqvc\Projects\test> ls
    
        Directory: C:\Users\xxqqvc\Projects\test
    
    
    Mode                LastWriteTime         Length Name
    ----                -------------         ------ ----
    -a----       2018-07-04     11:48            200 package.json
    
    
    PS C:\Users\xxqqvc\Projects\test> npm i --save yo
    
    > [email protected] postinstall C:\Users\xxqqvc\Projects\test\node_modules\spawn-sync
    > node postinstall
    
    
    > [email protected] postinstall C:\Users\xxqqvc\Projects\test\node_modules\yo
    > yodoctor
    
    
    Yeoman Doctor
    Running sanity checks on your system
    
    √ Global configuration file is valid
    √ NODE_PATH matches the npm root
    √ Node.js version
    √ No .bowerrc file in home directory
    √ No .yo-rc.json file in home directory
    { RequestError: connect ETIMEDOUT 104.18.97.96:443
        at ClientRequest.req.once.err (C:\Users\xxqqvc\Projects\test\node_modules\latest-version\node_modules\got\index.js:73:21)
        at Object.onceWrapper (events.js:273:13)
        at ClientRequest.emit (events.js:182:13)
        at TLSSocket.socketErrorListener (_http_client.js:382:9)
        at TLSSocket.emit (events.js:182:13)
        at emitErrorNT (internal/streams/destroy.js:82:8)
        at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
        at process._tickCallback (internal/process/next_tick.js:63:19)
      code: 'ETIMEDOUT',
      message: 'connect ETIMEDOUT 104.18.97.96:443',
      host: 'registry.npmjs.org',
      hostname: 'registry.npmjs.org',
      method: 'GET',
      path: '/yo' }
    × yo version
    { RequestError: connect ETIMEDOUT 104.18.97.96:443
        at ClientRequest.req.once.err (C:\Users\xxqqvc\Projects\test\node_modules\latest-version\node_modules\got\index.js:73:21)
        at Object.onceWrapper (events.js:273:13)
        at ClientRequest.emit (events.js:182:13)
        at TLSSocket.socketErrorListener (_http_client.js:382:9)
        at TLSSocket.emit (events.js:182:13)
        at emitErrorNT (internal/streams/destroy.js:82:8)
        at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
        at process._tickCallback (internal/process/next_tick.js:63:19)
      code: 'ETIMEDOUT',
      message: 'connect ETIMEDOUT 104.18.97.96:443',
      host: 'registry.npmjs.org',
      hostname: 'registry.npmjs.org',
      method: 'GET',
      path: '/yo' }
    × yo version
    
    Your yo version is outdated.
    
    Upgrade to the latest version by running:
    npm install -g yo@latest
    
    (node:6016) UnhandledPromiseRejectionWarning: Error: callback() can only be called once.
        at onetime (C:\Users\xxqqvc\Projects\test\node_modules\each-async\node_modules\onetime\index.js:15:11)
        at rule.verify.err (C:\Users\xxqqvc\Projects\test\node_modules\yeoman-doctor\lib\index.js:23:7)
        at binVersionCheck.then (C:\Users\xxqqvc\Projects\test\node_modules\yeoman-doctor\lib\rules\yo-version.js:21:23)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    (node:6016) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
    (node:6016) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
    √ npm version
    
    Found potential issues on your machine :(
    npm notice created a lockfile as package-lock.json. You should commit this file.
    npm WARN [email protected] No description
    npm WARN [email protected] No repository field.
    
    + [email protected]
    added 535 packages from 262 contributors and audited 1892 packages in 281.485s
    found 0 vulnerabilities
    
    opened by Olian04 36
  • Arrow keys not always working Windows 10 cmd

    Arrow keys not always working Windows 10 cmd

    When I use yo from Windows 10 cmd, the arrow keys are not always working. It then sticks into some kind of readline history list. This is not always happening. Unfortunately I can't pinpoint what is causing it. Using yo version 1.4.8.

    bug 
    opened by cveld 29
  • Can't install 1.8.2

    Can't install 1.8.2

    When I try npm i -g yo : node v4.4.4 (also try with 4.3.1) npm v3.9.0

    deprecated [email protected]: this package has been reintegrated into npm and is now out of date with respect to npm
    npm ERR! Darwin 15.5.0
    npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "[email protected]"
    npm ERR! node v4.4.4
    npm ERR! npm  v3.9.0
    npm ERR! path /usr/local/lib/node_modules/yo/lib/cli.js
    npm ERR! code ENOENT
    npm ERR! errno -2
    npm ERR! syscall chmod
    
    npm ERR! enoent ENOENT: no such file or directory, chmod '/usr/local/lib/node_modules/yo/lib/cli.js'
    npm ERR! enoent ENOENT: no such file or directory, chmod '/usr/local/lib/node_modules/yo/lib/cli.js'
    npm ERR! enoent This is most likely not a problem with npm itself
    npm ERR! enoent and is related to npm not being able to find a file.
    npm ERR! enoent 
    
    npm ERR! Please include the following file with any support request:
    npm ERR!     /Users/jaumard/Downloads/testTrails/npm-debug.log
    

    If I install npm i -g [email protected] all is working

    opened by jaumard 28
  • insight-yo.json

    insight-yo.json

    run yo webapp, and the err show:

    Error: EACCES, permission denied '/root/.config/configstore/insight-yo.json'
    You don't have access to this file.
    
        at Error (native)
        at Object.fs.openSync (fs.js:502:18)
        at Object.fs.readFileSync (fs.js:354:15)
        at Object.create.all.get (/usr/local/lib/node_modules/yo/node_modules/configstore/index.js:27:26)
        at Object.Configstore (/usr/local/lib/node_modules/yo/node_modules/configstore/index.js:20:44)
        at new Insight (/usr/local/lib/node_modules/yo/node_modules/insight/lib/index.js:37:34)
        at Object.<anonymous> (/usr/local/lib/node_modules/yo/lib/cli.js:130:15)
        at Module._compile (module.js:460:26)
        at Object.Module._extensions..js (module.js:478:10)
        at Module.load (module.js:355:32)
    

    when I run the commandls /root/.config/configstore, the result is:

    bower-github.yml  insight-bower.yml  update-notifier-bower.yml
    

    HELP !!

    opened by lizhengnacl 27
  • Error on installing yo package

    Error on installing yo package "npm install -g yo" - Failed at the [email protected] postinstall script 'yodoctor'

    Hi guys, I got some trouble on installing Yeoman 1.6.0

    Here my environement set :

    • Macbook Air Mavericks (10.9.5)
    • Fresh install of node and npm via node pkg installer -> https://nodejs.org/en/
    • echo $PATH => /usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/git/bin
    • node -e 'console.log(process.platform, process.versions)' => darwin { http_parser: '2.6.0', node: '5.4.1', v8: '4.6.85.31', uv: '1.8.0', zlib: '1.2.8', ares: '1.10.1-DEV', icu: '56.1', modules: '47', openssl: '1.0.2e' }
    • npm -v => 3.5.3

    Here the output error on installing =>

    MacBook-Air-de-Farah:~ farah$ sudo npm install -g yo npm WARN deprecated [email protected]: this package has been reintegrated into npm and is now out of date with respect to npm /usr/local/bin/yo -> /usr/local/lib/node_modules/yo/lib/cli.js

    [email protected] postinstall /usr/local/lib/node_modules/yo yodoctor

    env: node: No such file or directory npm ERR! Darwin 13.4.0 npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "yo" npm ERR! node v5.4.1 npm ERR! npm v3.5.3 npm ERR! file sh npm ERR! code ELIFECYCLE npm ERR! errno ENOENT npm ERR! syscall spawn

    npm ERR! [email protected] postinstall: yodoctor npm ERR! spawn ENOENT npm ERR! npm ERR! Failed at the [email protected] postinstall script 'yodoctor'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the yo package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! yodoctor npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs yo npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls yo npm ERR! There is likely additional logging output above.

    npm ERR! Please include the following file with any support request: npm ERR! /Users/farah/npm-debug.log

    yeoman install - failed at the yo 1 6 0 postinstall script yodoctor

    I can install other npm package without troubles. Node and npm are both already up to date. I already completely uninstall and reinstall node and npm. I also trying clean npm cache using npm cache clean -f before run npm install -g yo

    I also followed some same bug issue https://github.com/yeoman/yo/issues/213 and https://github.com/yeoman/yeoman/issues/1439 but no one resolved my problem

    I even tried to install with the first node version available for [email protected] which is node v.012.0 but I got exactly the same error yeoman install with node v0 12 0 - failed at the yo 1 6 0 postinstall script yodoctor

    Then I get back to my latest node version (5.4.1), I installed "yeoman-doctor" via npm install yeoman-doctor with success. Here is the output of yodoctor yodoctor result

    I retrying to install "yo" npm install -g yo but I got exactly the same error as the begening.

    Any help ? ^^

    Thanks, best regards

    opened by soufyan 25
  • 1.3.3 - ReferenceError: parent is not defined

    1.3.3 - ReferenceError: parent is not defined

    Having some trouble running yo

    I keep getting the following usr/local/lib/node_modules/yo/node_modules/yeoman-environment/node_modules/inquirer/node_modules/rx/dist/rx.all.js:9229 throw e; ^ ReferenceError: parent is not defined at AnonymousObserver._onNext (/usr/local/lib/node_modules/yo/node_modules/yeoman-environment/node_modules/inquirer/node_modules/rx/dist/rx.all.js:4259:63) at AnonymousObserver.Rx.AnonymousObserver.AnonymousObserver.next (/usr/local/lib/node_modules/yo/node_modules/yeoman-environment/node_modules/inquirer/node_modules/rx/dist/rx.all.js:1863:12) at AnonymousObserver.Rx.internals.AbstractObserver.AbstractObserver.onNext (/usr/local/lib/node_modules/yo/node_modules/yeoman-environment/node_modules/inquirer/node_modules/rx/dist/rx.all.js:1795:35) at AutoDetachObserverPrototype.next (/usr/local/lib/node_modules/yo/node_modules/yeoman-environment/node_modules/inquirer/node_modules/rx/dist/rx.all.js:9226:23) at AutoDetachObserver.Rx.internals.AbstractObserver.AbstractObserver.onNext (/usr/local/lib/node_modules/yo/node_modules/yeoman-environment/node_modules/inquirer/node_modules/rx/dist/rx.all.js:1795:35) at Subject.Rx.Subject.addProperties.onNext (/usr/local/lib/node_modules/yo/node_modules/yeoman-environment/node_modules/inquirer/node_modules/rx/dist/rx.all.js:9367:31) at AutoDetachObserverPrototype.next (/usr/local/lib/node_modules/yo/node_modules/yeoman-environment/node_modules/inquirer/node_modules/rx/dist/rx.all.js:9226:23) at AutoDetachObserver.Rx.internals.AbstractObserver.AbstractObserver.onNext (/usr/local/lib/node_modules/yo/node_modules/yeoman-environment/node_modules/inquirer/node_modules/rx/dist/rx.all.js:1795:35) at AutoDetachObserverPrototype.next (/usr/local/lib/node_modules/yo/node_modules/yeoman-environment/node_modules/inquirer/node_modules/rx/dist/rx.all.js:9226:23) at AutoDetachObserver.Rx.internals.AbstractObserver.AbstractObserver.onNext (/usr/local/lib/node_modules/yo/node_modules/yeoman-environment/node_modules/inquirer/node_modules/rx/dist/rx.all.js:1795:35)

    Environment Details OS: OS X 10.9.5 Node: v0.11.14 NPM: 2.1.11 Yo: 1.3.3 Bower: 1.3.12

    I ran npm install -g yo bower

    I have tried removing and reinstalling and npm update but nothing seems to work

    opened by scottyroges 25
  • Install Script Issues

    Install Script Issues

    I have seen issue 128 & 129, tried the solutions there, and I still get the same problem.

    npm i -g yo yields this:

    [email protected] postinstall /usr/local/lib/node_modules/yo node ./scripts/doctor

    sh: node: command not found npm ERR! [email protected] postinstall: node ./scripts/doctor npm ERR! Exit status 127 npm ERR! npm ERR! Failed at the [email protected] postinstall script. npm ERR! This is most likely a problem with the yo package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node ./scripts/doctor npm ERR! You can get their info via: npm ERR! npm owner ls yo npm ERR! There is likely additional logging output above.

    npm ERR! System Darwin 13.0.0 npm ERR! command "node" "/usr/local/bin/npm" "i" "-g" "yo" npm ERR! cwd /Users/billkracke/Dropbox/sites/clients/mission_coffee npm ERR! node -v v0.10.25 npm ERR! npm -v 1.3.24 npm ERR! code ELIFECYCLE npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /Users/billkracke/Dropbox/sites/clients/mission_coffee/npm-debug.log npm ERR! not ok code 0

    I cannot install

    opened by BillKracke 23
  • No such file or directory

    No such file or directory

    When I type yo in my terminal I get No such file or directory. I'm on Ubuntu 13.10 and Yeoman worked fine until yesterday. I've already tried to uninstall/reinstall and to update with sudo npm update -g.

    opened by Granze 20
  • Yo command outputs TypeError: path must be a string

    Yo command outputs TypeError: path must be a string

    Every time the command is run, it spits out the following error:

      return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                     ^
    TypeError: path must be a string
        at Object.fs.openSync (fs.js:427:18)
        at Object.fs.readFileSync (fs.js:284:15)
        at yoyo.Base.rootGeneratorName (/usr/local/lib/node_modules/yo/node_modules/yeoman-generator/lib/base.js:533:24)
        at yoyo.Base._setStorage (/usr/local/lib/node_modules/yo/node_modules/yeoman-generator/lib/base.js:542:34)
        at yoyo.Base (/usr/local/lib/node_modules/yo/node_modules/yeoman-generator/lib/base.js:85:8)
        at new yoyo (/usr/local/lib/node_modules/yo/bin/yoyo.js:12:18)
        at Environment.create (/usr/local/lib/node_modules/yo/node_modules/yeoman-generator/lib/env.js:366:10)
        at Environment.run (/usr/local/lib/node_modules/yo/node_modules/yeoman-generator/lib/env.js:409:24)
        at init (/usr/local/lib/node_modules/yo/bin/yo:97:7)
        at pre (/usr/local/lib/node_modules/yo/bin/yo:109:3)
    

    I have boiled it down to base.js line 533 being the culprit.

    opened by lushone 19
  • yo yo, may i help you?

    yo yo, may i help you?

    Here's our man, yo, being all helpful and stuff.

    (#34)

    Just a start! Anyone who has time to take a look and go, "Whoa dude, no," please do :)

    opened by stephenplusplus 19
  • Can't install Yeoman despite up to date Node and Npm

    Can't install Yeoman despite up to date Node and Npm

    Error

    Yeoman previously successfully installed and ran on the computer. Yesterday it was noted the Yo commands were no longer found, nor the Yo version despite not being uninstalled or files altered since last use. An attempt has been made to reinstall yeoman as it was no longer recognised, but it now appears impossible to install.


    My environment

    • OS version/details: Mac OS Ventura 13.0.1
    • Node version: v19.3.0
    • npm version: 9.2.0
    • Version of yo : N/A

    Expected behavior

    1. Update/Install Node to ensure up to date version
    2. Run npm install -g yo
    3. The terminal displays progress and confirms installation or shows an error
    4. Running yo --version reveals current version as proof of install

    Current behavior

    1. Clean reinstall of Node via Homebrew to ensure no errors
    2. Run npm install -g yo
    3. Terminal doesn't indicate errors and appears successful installation
    4. Yo commands are unsuccessful and 'command not found' is displayed

    Steps to reproduce the behavior

    Follow Tutorials set out at https://yeoman.io/learning/ or in the github

    install yo
    npm install --global yo
    
    install a generator
    npm install --global generator-webapp
    
     run it
    yo webapp
    

    Command line output

    Installation:

    npm WARN deprecated @npmcli/[email protected]: This functionality has been moved to @npmcli/fs
    npm WARN deprecated [email protected]: This functionality has been moved to @npmcli/fs
    npm WARN deprecated @npmcli/[email protected]: This functionality has been moved to @npmcli/fs
    
    changed 719 packages in 10s
    
    80 packages are looking for funding
      run npm fund for details
    

    But when checking version or trying to run other yo commands: -bash: yo: command not found

    opened by AmberRM99 1
  • Bump sinon from 12.0.1 to 15.0.1

    Bump sinon from 12.0.1 to 15.0.1

    Bumps sinon from 12.0.1 to 15.0.1.

    Changelog

    Sourced from sinon's changelog.

    15.0.1

    • aa493da4 Upgrade to fake-timers v10.0.2 (Carl-Erik Kopseng)

      Contains several fixes

    • b3ee0aa5 Use Node version 18 in Runkit examples (Carl-Erik Kopseng)

    Released by Carl-Erik Kopseng on 2022-12-15.

    15.0.0

    • b75fbfa9 Fix 2448: remove custom formatter (Morgan Roderick)

      Remove option to pass a custom formatter.

      The sub libraries of Sinon has long moved on to use util.inspect from Node. By using that in Sinon itself, we align all the libraries.

    Released by Morgan Roderick on 2022-11-28.

    14.0.2

    • 4d70f6e0 Upgrade nise to latest (Morgan Roderick)
    • 96a0d756 Update @​sinonjs/samsam to latest (Morgan Roderick)
    • babb4736 Prefer @​sinonjs/commons@​2 (Morgan Roderick)

      That makes ES2017 support explicit

    Released by Morgan Roderick on 2022-11-07.

    14.0.1

    • 6c4753ef Fixed CSS selectors in _base.scss and changed blockquote default size to 16px. (Jose Lupianez)
    • A bunch of dependency updates

    Released by Carl-Erik Kopseng on 2022-10-03.

    14.0.0

    Released by Morgan Roderick on 2022-05-07.

    ... (truncated)

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies javascript 
    opened by dependabot[bot] 0
  • Bump mocha from 9.1.3 to 10.2.0

    Bump mocha from 9.1.3 to 10.2.0

    Bumps mocha from 9.1.3 to 10.2.0.

    Release notes

    Sourced from mocha's releases.

    v10.2.0

    10.2.0 / 2022-12-11

    :tada: Enhancements

    • #4945: API: add possibility to decorate ESM name before import (@​j0tunn)

    :bug: Fixes

    :book: Documentation

    v10.1.0

    10.1.0 / 2022-10-16

    :tada: Enhancements

    :nut_and_bolt: Other

    v10.0.0

    10.0.0 / 2022-05-01

    :boom: Breaking Changes

    :nut_and_bolt: Other

    ... (truncated)

    Changelog

    Sourced from mocha's changelog.

    10.2.0 / 2022-12-11

    :tada: Enhancements

    • #4945: API: add possibility to decorate ESM name before import (@​j0tunn)

    :bug: Fixes

    :book: Documentation

    10.1.0 / 2022-10-16

    :tada: Enhancements

    :nut_and_bolt: Other

    10.0.0 / 2022-05-01

    :boom: Breaking Changes

    :nut_and_bolt: Other

    ... (truncated)

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies javascript 
    opened by dependabot[bot] 0
  • Seems yo do not support scoped package generator

    Seems yo do not support scoped package generator

    Seems yo do not support scoped package generator

    • OS version/details: mac - zsh and bash
    • Node version: 16.18.1
    • npm version: 8.19.2
    • Version of yo : 4.3.1
    npx --package yo --package @zh-mix/generator-mix -- yo --generators
    npx --package yo --package @zh-mix/generator-mix -- yo @zh-mix/mix
    
    image
    opened by arleyGuoLei 0
  • Bump got from 8.3.2 to 12.5.3

    Bump got from 8.3.2 to 12.5.3

    Bumps got from 8.3.2 to 12.5.3.

    Release notes

    Sourced from got's releases.

    v12.5.3

    • Fix abort event listeners not always being cleaned up (#2162) 3cc40b5

    https://github.com/sindresorhus/got/compare/v12.5.2...v12.5.3

    v12.5.2

    • Improve TypeScript 4.9 compatibility (#2163) 39f83b6

    https://github.com/sindresorhus/got/compare/v12.5.1...v12.5.2

    v12.5.1

    • Fix compatibility with TypeScript and ESM 3b3ea67
    • Fix request body not being properly cached (#2150) 3e9d3af

    https://github.com/sindresorhus/got/compare/v12.5.0...v12.5.1

    v12.5.0

    • Disable method rewriting on 307 and 308 status codes (#2145) e049e94
    • Upgrade dependencies 8630815 f0ac0b3 4c3762a

    https://github.com/sindresorhus/got/compare/v12.4.1...v12.5.0

    v12.4.1

    Fixes

    • Fix options.context being not extensible b671480715dbbff908e9a385f5e714570c663cd7
    • Don't emit uploadProgress after promise cancelation 693de217b030816f574d6e4cb505ee2e77b21c29

    https://github.com/sindresorhus/got/compare/v12.4.0...v12.4.1

    v12.4.0

    Improvements

    • Support FormData without known length (#2120) 850773c

    Fixes

    • Don&#39;t call beforeError hooks with HTTPError if the throwHttpErrors option is false (#2104) 3927348

    https://github.com/sindresorhus/got/compare/v12.3.1...v12.4.0

    v12.3.1

    • Don&#39;t freeze signal when freezing Options (#2100) 43b1467

    https://github.com/sindresorhus/got/compare/v12.3.0...v12.3.1

    v12.3.0

    • Add .off() method for events (#2092) 88056be

    https://github.com/sindresorhus/got/compare/v12.2.0...v12.3.0

    ... (truncated)

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies javascript 
    opened by dependabot[bot] 0
  • `yo` command to scaffold is stuck

    `yo` command to scaffold is stuck

    Hi,

    Windows 10 64-bit` My nodejs version is 10.22.1. The npm version is 6.14.6. yo version is 1.8.5. I'm in china, so I have some network firewall problem. I installed the yeoman through cnpm(v 7.1).

    I have a generator from OpenText called generator-csui-extension-21.1.0. (npm link ) Then I create a project folder and command 'yo csui-extension'. I get lots of error messages like the following:

    17 silly fetchPackageMetaData error for amodro-trace@^1.0.2 request to http://registry.cnpmjs.org/amodro-trace failed, reason: getaddrinfo EAI_AGAIN registry.cnpmjs.org registry.cnpmjs.org:80 18 silly fetchPackageMetaData error for csslint-stylish@^0.0.6 request to http://registry.cnpmjs.org/csslint-stylish failed, reason: getaddrinfo EAI_AGAIN registry.cnpmjs.org registry.cnpmjs.org:80 19 silly fetchPackageMetaData error for csso@^3.2.0 request to http://registry.cnpmjs.org/csso failed, reason: getaddrinfo EAI_AGAIN registry.cnpmjs.org registry.cnpmjs.org:80 20 silly fetchPackageMetaData error for eslint-config-defaults@^9.0.0 request to http://registry.cnpmjs.org/eslint-config-defaults failed, reason: getaddrinfo EAI_AGAIN registry.cnpmjs.org registry.cnpmjs.org:80

    I don't know how to deal with it. Does it mean I need to install these things one by one manually? I find there're many files in my project folder but there's nearly nothing in the project/node_modules folder.

    The worse thing is that yo can't scaffold after that. If I create a new folder like project B and yo csui-extension again. There's nothing happened except create a few of empty folders in project B. image image

    I tried to use 'yo doctor', it told me 'everything looks all right'.

    Does anyone have similar problems? What can I do to deal with it?

    opened by shirleyshan17 0
Releases(v4.3.1)
  • v4.3.1(Nov 7, 2022)

    • Remove insight module for now (#771) 1163e5d
    • Add dependabot config (#684) f7c0be1
    • Update dependencies

    https://github.com/yeoman/yo/compare/v4.3.0...v4.3.1

    Source code(tar.gz)
    Source code(zip)
  • v4.3.0(Jul 31, 2021)

    • Bump yeoman-doctor to 5.0.0 9e741c1
    • Bump yeoman-environment to 3.5.1 and unlock minor versions bump. e0a6ddc

    https://github.com/yeoman/yo/compare/v4.2.0...v4.3.0

    Source code(tar.gz)
    Source code(zip)
  • v4.2.0(May 20, 2021)

  • v4.1.0(May 2, 2021)

    • Bump yeoman-environment to 3.3.0 (#666) 967c2e1 Drops dependency with node 16 conflict.

    https://github.com/yeoman/yo/compare/v4.0.0...v4.1.0

    Source code(tar.gz)
    Source code(zip)
  • v4.0.0(Apr 22, 2021)

  • v4.0.0-beta.0(Mar 6, 2021)

    Breaking changes

    • Bump minimum require node to 12.10.0 62b5be2

    Features/Improvements

    • Bump yeoman-environment to 3.1.0 fd92eb8, d8049ec
    • Convert router to Promises/async. 2598967
    • Switch from listening to error event to catch rejected promise 5d533d7
    • Lookup is a sync method at environment 2.x and 3.x. ec362f3
    • Fix security warnings.

    https://github.com/yeoman/yo/compare/v3.1.1...v4.0.0-beta.0

    Source code(tar.gz)
    Source code(zip)
  • v3.1.0(Jul 4, 2019)

  • v3.0.0(Jul 1, 2019)

  • v2.0.6(Apr 14, 2019)

  • v2.0.4(Jul 10, 2018)

  • v2.0.3(Jun 28, 2018)

  • v2.0.2(Apr 14, 2018)

    Automatically setup http proxy tunneling to hopefully improve experience for users behind corporate proxies.

    The tunneling is handled by https://github.com/np-maintain/global-tunnel - check out this module if you need further instruction to set it up.

    Source code(tar.gz)
    Source code(zip)
  • v2.0.1(Jan 25, 2018)

  • v2.0.0(Jun 7, 2017)

  • v1.8.5(Sep 1, 2016)

  • v1.8.4(May 31, 2016)

  • v1.8.1(May 9, 2016)

  • v1.8.0(May 8, 2016)

  • v1.7.1(May 5, 2016)

    • Bump yeoman-environment explicitly so update-notifier will let the user know they need to update to support the latest yeoman-generator v0.23
    Source code(tar.gz)
    Source code(zip)
  • v1.7.0(Feb 26, 2016)

    New feature

    You can now run multiple generators in the same command. For that, just split each generators with commas (,)

    yo node --no-boilerplate, travis --language=node, license
    
    Source code(tar.gz)
    Source code(zip)
  • v1.6.0(Jan 8, 2016)

    Running generator by path

    New feature as parts of this release is the ability to pass a file path instead of a generator name. This would allow you to include generators as a living part your projects. For example:

    yo ./generator/controller
    

    Other improvements

    • Running yo webapp:<invalid subgenerator> won't fallback to yo webapp:app anymore.
    • Improvements to the error messages and failures.
    Source code(tar.gz)
    Source code(zip)
  • v1.5.1(Dec 23, 2015)

  • v1.5.0(Oct 31, 2015)

    Dependency updates and reduced install size.

    Note: We now recommend you have at least Node.js 4.2.0 and npm 3.3.0 installed. This is only a strong recommendation, not a requirement. Node.js 4.2.0 is the latest LTS version and npm 3.3.0 fixes a lot of issues. Upgrading will reduce the chances of you running into issues.

    Changes: https://github.com/yeoman/yo/compare/v1.4.8...v1.5.0

    Source code(tar.gz)
    Source code(zip)
  • v1.4.8(Sep 6, 2015)

    UI improvements

    • Now showing generator descriptions in the search page
    • Some colors and style improvements

    Other changes

    • Define minimal Node version as 0.12. Node 0.10 will continue working for the time being, but you'll see a warning at install time. Time to think about upgrading.
    Source code(tar.gz)
    Source code(zip)
  • 1.4.7(May 30, 2015)

  • v1.4.6(Mar 4, 2015)

  • v1.4.5(Jan 26, 2015)

  • v1.4.4(Jan 21, 2015)

  • v1.4.2(Jan 11, 2015)

    Add back raw CLI flags #274. These are deprecated, but lots of generators depend on it. Use the camelCased version instead. yo --foo-bar will be options.fooBar.

    Source code(tar.gz)
    Source code(zip)
  • v1.4.1(Jan 9, 2015)

    1.4.1 because 1.4.0 had a regression where a user couldn't run yo <generator>.

    1.4.0

    This release is mainly a huge internal update. We're hoping the code will now be easier to maintains and contribute to!

    New features

    • Search now add after each official generators name.
    • Yo now provide an option to delete the global prompt answer storage.

    Bug fixes

    • We're now using the npm couchdb (we were previously using the old mirror that wasn't in sync with npm anymore)

    Changes

    https://github.com/yeoman/yo/compare/v1.3.3...v1.4.1

    Source code(tar.gz)
    Source code(zip)
Owner
Yeoman
The web's scaffolding tool for modern webapps
Yeoman
LinkFree CLI is a command line tool that helps you to create your LinkFree profile through CLI.

LinkFree CLI LinkFree CLI is a command line tool that helps you to create your LinkFree profile through CLI. Demo Using the CLI (Commands) Note First

Pradumna Saraf 32 Dec 26, 2022
Pretty diff to html javascript cli (diff2html-cli)

diff2html-cli Diff to Html generates pretty HTML diffs from unified and git diff output in your terminal Table of Contents Features Online Example Dis

Rodrigo Fernandes 404 Dec 19, 2022
A cli tool to generate random mock data from OpenAPI definition for msw.

msw-auto-mock A cli tool to generate random mock data from OpenAPI descriptions for msw. Why We already have all the type definitions from OpenAPI spe

null 76 Dec 15, 2022
A simple CLI tool to create and manage xhelpers-api projects

A simple CLI tool to create and manage xhelpers-api projects

null 2 Feb 25, 2022
DataENV is a cli tool that allows you to save data temporarily using your terminal.

DataEnv CLI Instllation npm install -g dataenv Usage Table of Contents LocalStorage npx dataenv save Parameters npx dataenv show Parameters npx dataen

PGamerX 2 Feb 5, 2022
A CLI tool for project Pigeon.

Pigeon CLI [Incubating] A CLI tool for project Pigeon. Getting Start Download if you have node.js installed upon you machine, you can install pigeon-c

Pigeon 2 Feb 18, 2022
A CLI tool that allows you to ensure a database is live before closing the process

Wait for a database to be available prior to launching subsequent commands. ??⌛

Rida F'kih 3 Apr 16, 2022
Node.js CLI tool to generate a set of favicons from a single input file.

This is a simple CLI tool to generate an optimized set of favicons from a single input file. Icons are optimized in terms of both size and quantity (n

null 6 Nov 11, 2022
The easiest way of running code in a browser environment

browser-run The easiest way of running code in a browser environment. Bundles electronjs by default! Usage $ echo "console.log('Hey from ' + location)

Julian Gruber 415 Dec 19, 2022
Test your internet connection speed and ping using speedtest.net from the CLI

speed-test Test your internet connection speed and ping using speedtest.net from the CLI Install Ensure you have Node.js version 8+ installed. Then ru

Sindre Sorhus 3.8k Jan 7, 2023
Distributed, realtime CLI for live Node apps.

Vantage = CLI + SSH + REPL for your live node app. In one line: require("vantage")().listen(4000); What just happened? That's voodoo magic: show me th

dc 3.5k Dec 30, 2022
download torrents with node from the CLI

torrent Download torrents from the command line usage torrent <magnet link OR path to .torrent file> Download a torrent from a magnet link to torre

Max Ogden 619 Dec 26, 2022
:white_square_button: WhatsApp chat from commandline/console/cli using GoogleChrome puppeteer

Whatspup Use Whatsapp from commandline/console/cli using GoogleChrome puppeteer! ?? Features ✅ Send and receive messages ✅ Read Receipts ✅ Switch betw

Sarfraz Ahmed 343 Dec 1, 2022
:notes: Control iTunes via CLI

itunes-remote Control iTunes via your terminal ?? Using JXA via osascript via Node.js. Requirements Node.js (v0.12.7 or greater) Mac OS X (Yosemite 10

Michael Kühnel 422 Nov 19, 2022
Add stdin support to any CLI app that accepts file input

tmpin Add stdin support to any CLI app that accepts file input It pipes stdin to a temp file and spawns the chosen app with the temp file path as the

Sindre Sorhus 121 Oct 3, 2022
A CLI for peer-to-peer file sharing using the Hypercore Protocol.

A CLI for peer-to-peer file sharing (and more) using the Hypercore Protocol.

Hypercore Protocol 207 Dec 30, 2022
Node.js Open CLI Framework. Built with 💜 by Heroku.

oclif: Node.JS Open CLI Framework ?? Description ?? Getting Started Tutorial ✨ Features ?? Requirements ?? CLI Types ?? Usage ?? Examples ?? Commands

oclif 8k Jan 4, 2023
Git commit CLI

commitme Based on this gist by @gustavopch Installation You can install this on your package using npm i -D commitme or run it once using npx commitme

Roz 7 Jun 6, 2021