-
Notifications
You must be signed in to change notification settings - Fork 133
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
readme setup fixes #827
readme setup fixes #827
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
2. Build Nextra | ||
|
||
```bash | ||
npx turbo run build --filter={apps/nextra}... | ||
pnpm run build | ||
``` | ||
|
||
This will build `apps/nextra` and all local packages it depends on. | ||
|
||
3. Navigate to the correct subdirectory | ||
|
||
```sh | ||
cd apps/nextra | ||
``` | ||
|
||
4. Run the development server | ||
3. Run the development server | ||
|
||
```sh | ||
pnpm dev | ||
pnpm run dev | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the cd apps/nextra
step was removed, please specify that these commands should be run from the project root directory. This helps avoid confusion, as running pnpm run build
and pnpm run dev
from a different directory would fail. Consider either:
- Adding a note like "From the project root directory:" before the commands, or
- Restoring the
cd apps/nextra
step
Either approach would prevent a common source of confusion for developers following these instructions.
Spotted by Graphite Reviewer
Is this helpful? React 👍 or 👎 to let us know.
Description
Made updates to readme file to match my experience of getting it to work (ex: removed prebuild step which errors)
Checklist
pnpm fmt
?pnpm lint
?