Preview testing
Use the published pnport preview to test Turbopack and TypeScript 7 against a Yarn 4 Plug'n'Play project, without creating a physical project node_modules directory.
pnport 0.1.2 is available. See stable installation and known limits to use it. This walkthrough continues to pin the immutable preview. The experimental 0.1.0-next.1 preview is available on macOS and glibc Linux, each on x64 and arm64. Windows, musl hosts such as Alpine Linux, and mixed architectures are unsupported. Full feature, minimum-OS and benchmark acceptance remain unfinished; intermittent native initialization failures with exit status 125 remain under investigation. These workflows are for testing and do not certify compatibility with every project or tool.
On macOS, keep preview commands in the foreground with daemonization disabled: detached descendants can remain running after pnport stops. See filesystem and process limits.
Install the preview
Use Node.js 22 or newer; Node.js 24 is recommended for this walkthrough. Check the exact published version before installing it globally:
Keep optional dependencies enabled. Global installation keeps npm's physical node_modules directory out of the selected PnP project. See installation and availability for the project-local Yarn alternative and its package-age quarantine. With a project-local installation, replace pnport below with yarn pnport.
Prepare a PnP project
Use an existing Yarn 4 project. Run the following commands at its root, using a test branch or disposable copy if these settings differ from your project's configuration:
For the Turbopack workflow, keep the Yarn cache inside Turbopack's configured filesystem root. These settings place it inside the project; in a monorepo, ensure the configured root includes the shared cache.
Confirm that .pnp.cjs exists, then check readiness from the workspace where the command will run:
The report should contain "ready": true. This checks pnport's environment, not compatibility with a particular executable. pnport does not install dependencies or delete a conflicting physical node_modules directory. Resolve any reported conflict deliberately before retrying. See the command reference for project selection and binary resolution.
Run Turbopack
Use a Next.js project with next, react and react-dom installed. Your Next.js version must support the Turbopack flags shown below; see the Next.js CLI reference. In a monorepo, run these commands from the Next.js app workspace, where next is a direct dependency.
Start the development server:
Open the URL printed by Next.js, load a page, and edit its source to check that the change appears in the browser. Stop the development server with Ctrl+C before testing the production build:
After a successful build, start the production server and check the page again:
Stop it with Ctrl+C. Run the same build command again to check an unchanged rebuild, and record the Next.js version with pnport run -- next --version.
Run TypeScript 7
TypeScript 7 provides the native compiler through the typescript package and the tsc command. See the official TypeScript installation guide.
For a reproducible test, install the exact TypeScript 7.1 nightly used in pnport's macOS and Linux validation. Run this in the workspace you want to type-check:
The pinned nightly has the macOS signing entitlements pnport requires. The typescript@7.0.2 macOS binary lacks them and is rejected.
Confirm that a project without type errors exits with status 0. In a test copy, introduce a deliberate type error, rerun the check, and confirm that the compiler reports it and exits with a nonzero status; then restore the source.
For a project-reference build, use:
Report results
Report the OS version and CPU architecture, the exact command, whether it passed, and the Next.js or TypeScript 7 version. Include the following version and readiness information:
For a failure, include the exit status and error output. Remove credentials, private paths and project content before sharing diagnostics. Report reproducible results in issue #958, and see diagnostics and troubleshooting for exit codes and recovery.