Releases: yeoman/environment
Releases · yeoman/environment
v1.6.1
- Downgraded untildify to keep support for Node 0.12 and older.
v1.6.0
- 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
- Fix bug with local vs global install path priority
v1.5.2
- Fix regression to legacy yeoman-generator
hookFor
on windows.
v1.5.1
- Fix the regression to yeoman-generator legacy (pre 0.15)
hookFor()
we introduced in 1.5.0
v1.5.0
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
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
v1.2.7
Only remove lookups
that match full directory name. This fix edge cases like:
my-lib/generators/app
=> my-:app
, instead of my-lib:app
my.lib/generators/app
=> mylib:app
, instead of my.lib:app
test/generators/generators-thing
=> test:-thing
v1.2.6
Fix issue where more than 10 composed generators running at the same time would create event emitter leaks warnings. You can now compose as many generators as you want!