Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
^15.0.0 || ^16.0.0.next.config.mjs→next.config.tsand removes unusednodemon.json/plugin.spec.tsleftovers.tsconfig.jsontomodule: NodeNext/moduleResolution: NodeNext, which is required for Turbopack (the Next 16 default) to resolve.jsESM specifiers back to.ts/.tsxsources. WithBundlerresolution, Turbopack fails on imports likeexport { SearchBar } from '../components/SearchBar/SearchBar.js'(tracked upstream in Turbopack: support importing .ts/.tsx via .js extension (parity with webpack resolve.extensionAlias) vercel/next.js#82945).jsx: preserve→jsx: react-jsxand new.next/dev/typestsconfig additions.package.jsonfiles and pnpm workspace entries, moves dev dependencies to the plugin rootdevDependencies, rewritesdev/tsconfig.jsonto extend the root config with plugin alias paths, and adds.jsextensions to all relative imports for NodeNext resolution. This eliminates duplicate@payloadcms/uiinstances that causeduseConfig()/useField()context errors at runtime.Test plan
pnpm test:all— passes across all plugins (chat-agent 269, pages localized 64×2, unlocalized 12×2, multi-tenant 7×2, vercel-deployments 23, plus admin-search/alt-text/astro/content-translator Node strip-types suites)pnpm lint:all— 0 errors (warnings only, pre-existing)pnpm format:all— clean/admin: admin-search, alt-text/dev, alt-text/dev_unlocalized, chat-agent, cloudinary, content-translator, geocoding, pages/dev, pages/dev_multi_tenant, pages/dev_unlocalized, vercel-deployments → all HTTP 200