Comments (4)
my cli is 2.0.0-rc.1, but cli info say 1.0.0 (a bug?)
I confirm, if i type nest:
nest 2.0.0-rc.1
USAGE
nest <command> [options]
COMMANDS
new <name> [destination] Create a new Nest application
info Display Nest CLI information.
serve Start a hot reload development server.
generate <type> <name> Generate a new Nest asset
help <command> Display help for a specific command
GLOBAL OPTIONS
-h, --help Display help
-V, --version Display version
--no-color Disable colors
--quiet Quiet mode - only displays warn and error messages
-v, --verbose Verbose mode - will also output debug messages
MORE INFO
Nest.js CLI
but if i type nest info
_ _ _ ____ _ ___
| \ | | ___ ___| |_ / ___| | |_ _|
| \| |/ _ \/ __| __| | | | | | |
| |\ | __/\__ \ |_ | |___| |___ | |
|_| \_|\___||___/\__| \____|_____|___|
[System Information]
OS Version macOS High Sierra
NodeJS Version v6.9.5 Boron
NPM Version 5.6.0
[Nest Information]
NestJS Version 4.5.10
Nest CLI Version 1.0.0
from nest-cli.
Nest CLI Version 1.0.0 ?
Please upgrade to 2.0.0-rc.1 ;-)
from nest-cli.
Bugs found :
- handler async do some weird things
- asset emitter does not create module folder
About the info command bug :
- the code look at the project version not the CLI version
Let's fix it !
from nest-cli.
upgrade to 2.0.0-rc.2 to get generate fix
from nest-cli.
Related Issues (20)
- Unknown OS Version on newer os versions HOT 16
- The application won't reload after compiled OS X HOT 5
- Errors in default webpack config file (webpack.config.json) are silently ignored HOT 1
- Regression > Copying assets is broken on Windows devices
- Facing module unavailability error on changing the bundler to swc HOT 1
- odd behavior when the config file can't be read HOT 5
- Add remove command to delete a non-root project from monorepo and auto-update nest-cli.json HOT 2
- false-positive warning message for `@nestjs/schematics` HOT 1
- [Feature] - nestCLI option to generate Command and Events HOT 1
- Update gitignore to include more common files or folders HOT 5
- The `roodDir` compiler option not being respected when using SWC HOT 7
- add "compilerOptions.sourceMaps" option is nest-cli-json HOT 1
- Assets only works on top level project. HOT 1
- Clean up dependencies HOT 1
- Listing all the routes/endpoints with their types and middleware in project HOT 2
- Error cause is not logged in dev:watch mode HOT 1
- broken path in build output HOT 4
- CLI not work whit PowerShell HOT 3
- ERROR [I18nService] parsing translation error in 10.3.2 HOT 12
- Unable to upgrade to the latest version, node version is v16.20.2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from nest-cli.