[Tutorial Part 2] Oooops

OK I’ve moved On (or should that be got this far)
first command:
yarn rw setup tailwindcss
result in


PS D:\WEB\_nodejs\redwoodblog> yarn rw setup tailwindcss
yarn run v1.22.5
$ D:\WEB\_nodejs\redwoodblog\node_modules\.bin\rw setup tailwindcss
rw setup <commmand>

Initialize project config and install packages

Commands:
  rw setup auth <provider>   Generate an auth configuration
  rw setup custom-web-index  Set up a custom index.js file, so you can customise     
                             how Redwood web is mounted in your browser
  rw setup deploy <target>   Setup deployment to various targets
  rw setup generator <name>  Copies generator templates locally for
                             customization
  rw setup i18n              Set up i18n
  rw setup tsconfig          Set up tsconfig for web and api sides
  rw setup ui <library>      Set up a UI design or style library
  rw setup webpack           Set up webpack in your project so you can add
                             custom config

Options:
  --help     Show help                                                 [boolean]     
  --version  Show version number                                       [boolean]     
  --cwd      Working directory to use (where `redwood.toml` is located.)

Also see the Redwood CLI Reference
(​https://redwoodjs.com/reference/command-line-interface#setup​)

Not enough non-option arguments: got 0, need at least 1
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. 
PS D:\WEB\_nodejs\redwoodblog>
OK I now know what exit code 1 does to VSCode but what did I miss? some missing argument?? The spelling of command as "commmand" is intriguing :grin:
don't you just love error messages

Try “yarn rw setup ui tailwindcss”. See Docs - CLI Commands : RedwoodJS Docs

We’re in the process of updating Part 2 of the tutorial to match up with the upcoming v1.0 release of Redwood. This command did work at the time Part 2 was written but has since been updated to the that @dthyresson just mentioned above!

This will be fixed when the updates for Part 2 go live this week!

2 Likes

@dthyresson @rob Thanks that solved it (methinks I started too soon) difficult to consume all the docs at this stage

1 Like