Skip to content

Releases: yeoman/environment

v1.6.5

09 Oct 02:24
Compare
Choose a tag to compare
  • Improve error message

v1.6.2

06 Jul 17:57
Compare
Choose a tag to compare
  • Fix exception thrown when run outside a bin script

v1.6.1

02 May 18:09
Compare
Choose a tag to compare
  • Downgraded untildify to keep support for Node 0.12 and older.

v1.6.0

02 May 00:33
Compare
Choose a tag to compare
  • Update search paths for generators in hope to reduce errors people ran into with badly configured NODE_PATH or while using nvm.
  • Update to inquirer 1.0

v1.5.3

19 Apr 05:56
Compare
Choose a tag to compare
  • Fix bug with local vs global install path priority

v1.5.2

08 Jan 21:04
Compare
Choose a tag to compare
  • Fix regression to legacy yeoman-generator hookFor on windows.

v1.5.1

08 Jan 07:06
Compare
Choose a tag to compare
  • Fix the regression to yeoman-generator legacy (pre 0.15) hookFor() we introduced in 1.5.0

v1.5.0

27 Dec 03:08
Compare
Choose a tag to compare

Environment now doesn't recursively walks the namespace of a generator. This was confusing as yo node:something would end up running yo node instead of letting the user know that generator doesn't exist.

[Unpublished after breaking generator-angular]

v1.4.0

22 Dec 08:47
Compare
Choose a tag to compare

Run npm update -g yo to use the latest version.

Changes

  • Environment#get() now fallback to getting a generator by using a local path if there's no namespace matches (e.g. allowing things like yo ./path/to-generator)
  • The debug namespace is now DEBUG=yeoman:environment to be consistent with yeoman-generator

1.3.0

22 Oct 10:43
Compare
Choose a tag to compare

Update dependencies.

v1.2.7...v1.3.0