Sam Ko

Context from a support case sent to us. > I'm trying to test the `vercel alias` command. My terminal output and error are below: > > ~/sites/vercel-demo main +7 !1...

Add missing period

2

Missing a period here → https://turbo.build/repo/docs/reference/command-line-reference#--filter. 

Refactor Next.js CLI to use Commander

2

## Description ... ## Changes ... Closes NEXT-2293

refactor(cli): refactor cli to commander

2

## Changes ... ## Description ...

The root `--help` doesn't respect `.usage()` in a command

2

## Example ``` .usage('[directory] [options]') ```  Let me know if I'm missing something here! On the latest version v12.

chore: migrate formatting to biome

3

## Why? [Biome](https://biomejs.dev) (for just formatting so far) performs ~9x faster than [Prettier](https://prettier.io) for the repo locally. ![CleanShot 2024-06-28 at [email protected]](https://graphite-user-uploaded-assets-prod.s3.amazonaws.com/FEMDaE9e61ZMCiJM0S0I/c3b3e088-8abc-4a2e-a93b-fbc2984b9786.jpg)

fix: styledComponents schema

4

## Why? Both the `topLevelImportPaths` and `meaninglessFilenames` should not need a minimal of 1 item in their arrays. - Fixes https://github.com/vercel/next.js/issues/68573

docs(ppr): remove v14 mention for ppr

1

## Why? For PPR (experimental), user's should just opt to use v15 canary if they want to try out PPR. Removing the v14 mention reduces this confusion.

docs(ppr): update note about ppr

1

## Why? Let's clarify this is only available in canary. We need to remove it from the stable docs later.

fix: uri encode dynamic routes in dev

4

## Why? In `next dev`, `404` errors are returned for dynamic routes that contain characters that should be URI encoded in the path. The `404`s are not present in `next...