Attached at the end is the log: note the 107.20s. clock time
I used many different JavaScript development tools and frameworks - all of them take a lot less time to create the minimalistic app skeleton. Even making the needed accommodation for the fact that RW creates the full-stack app, 107.2 secs is a too big number.
Probably the fastest way to address this initially is to not run the yarn install as a part of the first-time app creation, resulting in 107.0 shrunk to likely 15.0 The developer would have to type both commands yarn create redwood-app ./test followed by yarn install - the developer would not mind that and RW would not be blamed for a long lasting install phase.
I am not sure how to handle the creation of the information which follows the yarn install (is there some "callback" for yarn install??)
yarn create redwood-app ./test
yarn create v1.22.5
[1/4] Resolving packages...
[2/4] Fetching packages...
info [email protected]: The platform "win32" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Installed "[email protected]" with binaries:
- create-redwood-app
√ Creating Redwood app
√ Creating directory 'c:\work\temp1\test'
√ Installing packages
√ Checking node and yarn compatibility
√ Running 'yarn install'... (This could take a while)
Thanks for trying out Redwood!
We've created your app in 'c:\work\temp1\test'
Enter the directory and run 'yarn rw dev' to start the development server.
⚡️ Get up and running fast with this Quick Start guide: https://redwoodjs.com/docs/quick-start
Join the Community
❖ Join our Forums: https://community.redwoodjs.com
❖ Join our Chat: https://discord.gg/redwoodjs
Get some help
❖ Get started with the Tutorial: https://redwoodjs.com/tutorial
❖ Read the Documentation: https://redwoodjs.com/docs
Stay updated
❖ Sign up for our Newsletter: https://www.redwoodjs.com/newsletter
❖ Follow us on Twitter: https://twitter.com/redwoodjs
Become a Contributor ❤
❖ Learn how to get started: https://redwoodjs.com/docs/contributing
❖ Find a Good First Issue: https://redwoodjs.com/good-first-issue
Done in 107.20s.
Attached at the end is the log: note the 107.20s. clock time
I used many different JavaScript development tools and frameworks - all of them take a lot less time to create the minimalistic app skeleton. Even making the needed accommodation for the fact that RW creates the full-stack app, 107.2 secs is a too big number.
Probably the fastest way to address this initially is to not run the
yarn installas a part of the first-time app creation, resulting in 107.0 shrunk to likely 15.0 The developer would have to type both commandsyarn create redwood-app ./testfollowed byyarn install- the developer would not mind that and RW would not be blamed for a long lastinginstallphase.I am not sure how to handle the creation of the information which follows the
yarn install(is there some "callback" foryarn install??)