Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Remove next-dev and its test suite and benchmarks #55983

Merged
merged 3 commits into from
Sep 26, 2023
Merged

Remove next-dev and its test suite and benchmarks #55983

merged 3 commits into from
Sep 26, 2023

Commits on Sep 25, 2023

  1. Remove next-dev and its test suite and benchmarks 

    We've rearchitected Next.js+Turbopack so Turbopack does not run reimplement pieces of Next.js in its devserver. This:

- Removes the `next-dev` binary, which is no longer reachable through `next --turbo`.
- Removes its test suite, as much of it is tested (and often more thoroughly) by the Next.js test suite
- Removes its benchmark suite, which should be covered by `Turbopack-bench` by https://github.com/vercel/turbo/tree/main/crates/turbopack-bench

Test Plan: CI
    @wbinnssmith
    wbinnssmith committed Sep 25, 2023
    Configuration menu
    Copy the full SHA
    7b0eeff View commit details
    Browse the repository at this point in the history

  2. fixup! Remove next-dev and its test suite and benchmarks

    @wbinnssmith
    wbinnssmith committed Sep 25, 2023
    Configuration menu
    Copy the full SHA
    721833c View commit details
    Browse the repository at this point in the history

  3. fixup! Remove next-dev and its test suite and benchmarks

    @wbinnssmith
    wbinnssmith committed Sep 25, 2023
    Configuration menu
    Copy the full SHA
    263029c View commit details
    Browse the repository at this point in the history