-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ng g app --dry-run
and ng g lib --dry-run
are slow
#706
Comments
bcabanes
added a commit
to bcabanes/nx
that referenced
this issue
Aug 16, 2018
Currently the `dry-run` command speed is on an average of: * `ng g app app_name --dry-run`: 7099.051ms to 7207.579ms; * `ng g lib lib_name --dry-run`: 4015.622ms to 3881.893ms; This is due to too many files in the tree. While performing the transformation required by the schematic, the tree inclues files in the _node_modules, .git, .idea, .vscode_ folders. These files are not needed and impact the performance of the commandline. This add a filter function on the tree, before anything is moved. With that filter function the average speed is: * `ng g app app_name --dry-run`: 1420.826ms to 1435.487ms; * `ng g lib lib_name --dry-run`: 1382.279ms to 1413.042ms; close nrwl#706
bcabanes
added a commit
to bcabanes/nx
that referenced
this issue
Aug 17, 2018
Currently the `dry-run` command speed is on an average of: * `ng g app app_name --dry-run`: 7099.051ms to 7207.579ms; * `ng g lib lib_name --dry-run`: 4015.622ms to 3881.893ms; This is due to too many files in the tree. While performing the transformation required by the schematic, the tree inclues files in the _node_modules, .git, .idea, .vscode_ folders. These files are not needed and impact the performance of the commandline. This add a filter function on the tree, before anything is moved. With that filter function the average speed is: * `ng g app app_name --dry-run`: 1420.826ms to 1435.487ms; * `ng g lib lib_name --dry-run`: 1382.279ms to 1413.042ms; close nrwl#706
bcabanes
added a commit
to bcabanes/nx
that referenced
this issue
Aug 17, 2018
Currently the `dry-run` command speed is on an average of: * `ng g app app_name --dry-run`: 7099.051ms to 7207.579ms; * `ng g lib lib_name --dry-run`: 4015.622ms to 3881.893ms; This is due to too many files in the tree. While performing the transformation required by the schematic, the tree inclues files in the _node_modules, .git, .idea, .vscode_ folders. These files are not needed and impact the performance of the commandline. This add a filter function on the tree, before anything is moved. With that filter function the average speed is: * `ng g app app_name --dry-run`: 1420.826ms to 1435.487ms; * `ng g lib lib_name --dry-run`: 1382.279ms to 1413.042ms; close nrwl#706
bcabanes
added a commit
to bcabanes/nx
that referenced
this issue
Aug 17, 2018
Currently the `dry-run` command speed is on an average of: * `ng g app app_name --dry-run`: 7099.051ms to 7207.579ms; * `ng g lib lib_name --dry-run`: 4015.622ms to 3881.893ms; This is due to too many files in the tree. While performing the transformation required by the schematic, the tree inclues files in the _node_modules, .git, .idea, .vscode_ folders. These files are not needed and impact the performance of the commandline. This add a filter function on the tree, before anything is moved. With that filter function the average speed is: * `ng g app app_name --dry-run`: 1420.826ms to 1435.487ms; * `ng g lib lib_name --dry-run`: 1382.279ms to 1413.042ms; close nrwl#706
bcabanes
added a commit
to bcabanes/nx
that referenced
this issue
Aug 17, 2018
Currently the `dry-run` command speed is on an average of: * `ng g app app_name --dry-run`: 7099.051ms to 7207.579ms; * `ng g lib lib_name --dry-run`: 4015.622ms to 3881.893ms; This is due to too many files in the tree. While performing the transformation required by the schematic, the tree inclues files in the _node_modules, .git, .idea, .vscode_ folders. These files are not needed and impact the performance of the commandline. This add a filter function on the tree, before anything is moved. With that filter function the average speed is: * `ng g app app_name --dry-run`: 1420.826ms to 1435.487ms; * `ng g lib lib_name --dry-run`: 1382.279ms to 1413.042ms; close nrwl#706
vsavkin
pushed a commit
that referenced
this issue
Aug 20, 2018
Currently the `dry-run` command speed is on an average of: * `ng g app app_name --dry-run`: 7099.051ms to 7207.579ms; * `ng g lib lib_name --dry-run`: 4015.622ms to 3881.893ms; This is due to too many files in the tree. While performing the transformation required by the schematic, the tree inclues files in the _node_modules, .git, .idea, .vscode_ folders. These files are not needed and impact the performance of the commandline. This add a filter function on the tree, before anything is moved. With that filter function the average speed is: * `ng g app app_name --dry-run`: 1420.826ms to 1435.487ms; * `ng g lib lib_name --dry-run`: 1382.279ms to 1413.042ms; close #706
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
They should be very fast, but instead takes many seconds.
The text was updated successfully, but these errors were encountered: