Use JSONC for default server-external-packages #86252
Conversation
ijjk
added
created-by: Turbopack team
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Failing test suitesCommit: 355d7da | About building and testing Next.js
Expand output● Production Usage › should navigate through history after query update ● Production Usage › should handle query/hash correctly during query updating #hello? $search ● Production Usage › should handle query/hash correctly during query updating #? $search ● Production Usage › should handle query/hash correctly during query updating ## $search ● Production Usage › should handle query/hash correctly during query updating ##? $search ● Production Usage › should handle query/hash correctly during query updating ##hello? $search ● Production Usage › should handle query/hash correctly during query updating ##hello $search ● Production Usage › should handle query/hash correctly during query updating #hello?world $search ● Production Usage › should handle query/hash correctly during query updating #a ?hello=world ● Production Usage › should handle query/hash correctly during query updating #a ?hello ● Production Usage › should handle query/hash correctly during query updating #a ?hello= ● Production Usage › should not show target deprecation warning ● Production Usage › should respond with 405 for POST to static page ● Production Usage › should contain generated page count in output ● Production Usage › should output traces ● Production Usage › should not contain currentScript usage for publicPath ● Production Usage › should not contain rsc APIs in main chunk ● Production Usage › With basic usage › should render the page ● Production Usage › With basic usage › should polyfill Node.js modules ● Production Usage › With basic usage › should allow etag header support ● Production Usage › With basic usage › should allow etag header support with getStaticProps ● Production Usage › With basic usage › should allow etag header support with getServerSideProps ● Production Usage › With basic usage › should have X-Powered-By header support ● Production Usage › With basic usage › should render 404 for routes that do not exist ● Production Usage › With basic usage › should render 404 for /_next/static route ● Production Usage › With basic usage › should render 200 for POST on page ● Production Usage › With basic usage › should render 404 for POST on missing page ● Production Usage › With basic usage › should render 404 for _next routes that do not exist ● Production Usage › With basic usage › should render 404 even if the HTTP method is not GET or HEAD ● Production Usage › With basic usage › should render 404 for dotfiles in /static ● Production Usage › With basic usage › should return 405 method on static then GET and HEAD ● Production Usage › With basic usage › should return 412 on static file when If-Unmodified-Since is provided and file is modified ● Production Usage › With basic usage › should return 200 on static file if If-Unmodified-Since is invalid date ● Production Usage › With basic usage › should set Content-Length header ● Production Usage › With basic usage › should set Cache-Control header ● Production Usage › With basic usage › should set correct Cache-Control header for static 404s ● Production Usage › With basic usage › should block special pages ● Production Usage › With basic usage › should not contain customServer in NEXT_DATA ● Production Usage › API routes › should work with pages/api/index.js ● Production Usage › API routes › should work with pages/api/hello.js ● Production Usage › API routes › does not work with pages/api/readfile-dirname.js ● Production Usage › API routes › should work with pages/api/readfile-processcwd.js ● Production Usage › API routes › should work with dynamic params and search string ● Production Usage › With navigation › should navigate via client side ● Production Usage › With navigation › should navigate to nested index via client side ● Production Usage › With navigation › should reload page successfully (on bad link) ● Production Usage › With navigation › should reload page successfully (on bad data fetch) ● Production Usage › should navigate to external site and back ● Production Usage › should navigate to page with CSS and back ● Production Usage › should navigate to external site and back (with query) ● Production Usage › should change query correctly ● Production Usage › Runtime errors › should render a server side error on the client side ● Production Usage › Runtime errors › should render a client side component error ● Production Usage › Runtime errors › should call getInitialProps on _error page during a client side component error ● Production Usage › Misc › should handle already finished responses ● Production Usage › Misc › should allow to access /static/ and /_next/ ● Production Usage › Misc › Should allow access to public files ● Production Usage › Misc › should reload the page on page script error ● Production Usage › Misc › should add autoExport for auto pre-rendered pages ● Production Usage › Misc › should not add autoExport for non pre-rendered pages ● Production Usage › Misc › should add prefetch tags when Link prefetch prop is used ● Production Usage › Misc › It does not add a timestamp to link tags with prefetch attribute ● Production Usage › Misc › should reload the page on page script error with prefetch ● Production Usage › should not expose the compiled page file in development ● Production Usage › should not put backslashes in pages-manifest.json ● Production Usage › should handle failed param decoding ● Production Usage › should replace static pages with HTML files ● Production Usage › should not replace non-static pages with HTML files ● Production Usage › should warn when prefetch is true ● Production Usage › should not emit stats ● Production Usage › should contain the Next.js version in window export ● Production Usage › should clear all core performance marks ● Production Usage › should not clear custom performance marks ● Production Usage › should have defer on all script tags ● Production Usage › should only have one DOCTYPE ● Production Usage › should preserve query when hard navigating from page 404 ● Production Usage › should remove placeholder for next/image correctly ● Production Usage › Dynamic import › default behavior › should render dynamic import components ● Production Usage › Dynamic import › default behavior › should render one dynamically imported component and load its css files ● Production Usage › Dynamic import › default behavior › should render three dynamically imported components and load their css files ● Production Usage › Dynamic import › default behavior › should bundle two css modules for one dynamically imported component into one css file ● Production Usage › Dynamic import › default behavior › should bundle two css modules for nested components into one css file ● Production Usage › Dynamic import › default behavior › should not remove css styles for same css file between page transitions ● Production Usage › Dynamic import › default behavior › should output correct css even in case of three css module files while one is shared across files ● Production Usage › Dynamic import › default behavior › should render one dynamically imported component without any css files ● Production Usage › Dynamic import › default behavior › should render even there are no physical chunk exists ● Production Usage › Dynamic import › ssr:false option › should not render loading on the server side ● Production Usage › Dynamic import › ssr:false option › should render the component on client side ● Production Usage › Dynamic import › ssr:true option › should render the component on the server side ● Production Usage › Dynamic import › ssr:true option › should render the component on client side ● Production Usage › Dynamic import › custom loading › should render custom loading on the server side when ● Production Usage › Dynamic import › custom loading › should render the component on client side ● Production Usage › process.env › should set process.env.NODE_ENV in production ● Production Usage › process.browser › should eliminate server only code on the client ● Production Usage › process.browser › should eliminate client only code on the server ● Production Usage › With Security Related Issues › should handle invalid URL properly ● Production Usage › With Security Related Issues › should only access files inside .next directory ● Production Usage › With Security Related Issues › should not allow accessing files outside .next/static directory ● Production Usage › With Security Related Issues › should not leak the user's home directory into the build ● Production Usage › With Security Related Issues › should prevent URI based XSS attacks ● Production Usage › With Security Related Issues › should prevent URI based XSS attacks using single quotes ● Production Usage › With Security Related Issues › should prevent URI based XSS attacks using double quotes ● Production Usage › With Security Related Issues › should prevent URI based XSS attacks using semicolons and double quotes ● Production Usage › With Security Related Issues › should prevent URI based XSS attacks using semicolons and single quotes ● Production Usage › With Security Related Issues › should prevent URI based XSS attacks using src ● Production Usage › With Security Related Issues › should prevent URI based XSS attacks using querystring ● Production Usage › With Security Related Issues › should prevent URI based XSS attacks using querystring and quotes ● Production Usage › With Security Related Issues › should handle encoded value in the pathname correctly \ ● Production Usage › With Security Related Issues › should handle encoded value in the pathname correctly % ● Production Usage › With Security Related Issues › should handle encoded value in the query correctly ● Production Usage › With Security Related Issues › should handle encoded value in the pathname correctly / ● Production Usage › With Security Related Issues › should handle encoded value in the pathname to query correctly (/) ● Production Usage › With Security Related Issues › should handle encoded / value for trailing slash correctly ● Production Usage › With Security Related Issues › should not execute script embedded inside svg image, even if dangerouslyAllowSVG=true
Expand output● app dir - duplicate layout components › should not duplicate layout elements when navigating to 404
Expand output● next-config-ts-async-function-cjs › should support config as async function (CJS)
Expand output● Document and App › should not have any missing key warnings
Expand output● app-dynamic-error › production mode › throws an error when prerendering a page with config dynamic error
Expand output● initial-css-order › should serve styles in the correct order for the page ● initial-css-order › should serve styles in the correct order for global-not-found
Expand output● dev-fetch-hmr › should retain module level fetch patching
Expand output● global-not-found - cache-components › should render global-not-found for 404 routes ● global-not-found - cache-components › should render not-found boundary when calling notFound() in a page
Expand output● 404 Page Support SSG › development mode › should respond to 404 correctly ● 404 Page Support SSG › development mode › should render error correctly ● 404 Page Support SSG › development mode › should render index page normal
Expand output● Promise in next config › production mode › should warn when a promise is returned on webpack
Expand output● Auto Export _error bail › production mode › should not opt-out of auto static optimization from invalid _error
Expand output● HMR symlinks › tracks updates to symlinked target ● HMR symlinks › tracks updates to the symlink ● HMR symlinks › tracks updates to the middle of a symlink chain
Expand output● next-config-ts-export-as-default-esm › should support export as default (ESM)
Expand output● app dir - with proxy in src dir › works without crashing when using RequestStore
Expand output● Auto Export › production mode › should show warning for query provided for auto exported page correctly
Expand output● app dir - css - experimental inline css › Production only › should render page with correct styles ● app dir - css - experimental inline css › Production only › should not return rsc payload with inlined style as a dynamic client nav ● app dir - css - experimental inline css › Production only › should have only one style tag when navigating from page with inlining to page without inlining ● app dir - css - experimental inline css › Production only › should apply font styles correctly via className ● app dir - css - experimental inline css › Production only › should apply font styles correctly via CSS variable ● app dir - css - experimental inline css › Production only › should inline font-face with absolute src URL
Expand output● Rewritten API Requests should pass OPTIONS requests to the api function › should pass OPTIONS requests to the api function
Expand output● Dynamic route rename casing › should not throw error when changing casing of dynamic route file
Expand output● app type checking - production mode › should report link errors ● app type checking - production mode › should generate route types correctly and report router API errors ● app type checking - production mode › should generate route types correctly and report form errors ● app type checking - production mode › should generate route types correctly and report redirect errors
Expand output● Fallback Modules › production mode › Crypto Application › should not include crypto
Expand output● devtools-position-bottom-right › should devtools indicator position initially be bottom-right when configured
Expand output● build trace with extra entries in monorepo › production mode › should build and trace correctly
Expand output● hmr-app-and-pages › should do HMR when app router and pages router have shared CSS
Expand output● custom-app-server-action-redirect › redirects with basepath properly when server action handler uses ● custom-app-server-action-redirect › redirects with proper cookies set from both redirect response and post respose
Expand output● HMR Move File › should work when moving a component to another directory
Expand output● Handles an Error in _error › production mode › Handles error during SSR ● Handles an Error in _error › production mode › Handles error during client transition
Expand output● app-dir - action-in-pages-router › should not error on fake server action in pages router
Expand output● app-dir action useActionState › should support submitting form state with JS ● app-dir action useActionState › should support submitting form state without JS ● app-dir action useActionState › should support hydrating the app from progressively enhanced form request ● app-dir action useActionState › should send the action to the provided permalink with form state when JS disabled
Expand output● css-media-query › should preserve max-width media query syntax instead of transpiling to range syntax ● css-media-query › should apply the correct styles based on media query
Expand output● catchall-specificity › should match the generic catchall correctly ● catchall-specificity › should match the specific catchall correctly
Expand output● app-dir absolute assetPrefix › bundles should return 200 on served assetPrefix
Expand output● hydration-error-count › should have correct hydration error count for bad nesting ● hydration-error-count › should have correct hydration error count for html diff ● hydration-error-count › should display correct hydration info in each hydration error view ● hydration-error-count › should display runtime error separately from hydration errors
Expand output● app-dir action handling › should handle actions correctly after navigation / redirection events ● app-dir action handling › should handle actions correctly after following a relative link
Expand output● devtools-position-default › should devtools indicator position initially be bottom-left by default
Expand output● build-error-logs › should only log error a single time
Expand output● dev-overlay - portal-not-affect-parent › should not affect parent display
Expand output● hydrate/render ordering › production mode › correctly measures hydrate followed by render
Expand output● Cache Components Dev Errors › should not show a red box error on the SSR render ● Cache Components Dev Errors › should show a red box error on the SSR render when data is uncached
Expand output● app-dir edge SSR invalid reexport › should warn or error about the re-export of a pages runtime/preferredRegion config
Expand output● global-not-found - basic › should render global-not-found for 404 ● global-not-found - basic › should ssr global-not-found for 404 ● global-not-found - basic › should render not-found boundary when calling notFound() in a page
Expand output● bigint API route support › production mode › should return 200 ● bigint API route support › production mode › should return the BigInt result text
Expand output● app-fetch-errors › should still successfully render when a fetch request that acquires a cache lock errors
Expand output● Dotenv default expansion › should work
Expand output● App asPath › should not have any changes in asPath after a bundle rebuild
Expand output● Test suite failed to run
Expand output● De-dedupes scripts in _document › production mode › Does not have duplicate script references
Expand output● next-config-ts-import-from-node-modules-cjs › should import from node_modules (CJS)
Expand output● app-dir alias › should handle typescript paths alias correctly ● app-dir alias › should resolve css imports from outside with src folder presented
Expand output● app-dir action disallowed origins › should error if x-forwarded-host does not match the origin
Expand output● app dir client cache semantics (30s/5min) › prefetch={true} › should prefetch the full page ● app dir client cache semantics (30s/5min) › prefetch={true} › should re-use the cache for the full page, only for 5 mins ● app dir client cache semantics (30s/5min) › prefetch={true} › should prefetch again after 5 mins if the link is visible again ● app dir client cache semantics (30s/5min) › prefetch={false} › should not prefetch the page at all ● app dir client cache semantics (30s/5min) › prefetch={false} › should re-use the cache only for 30 seconds ● app dir client cache semantics (30s/5min) › prefetch={undefined} - default › should prefetch partially a dynamic page ● app dir client cache semantics (30s/5min) › prefetch={undefined} - default › should re-use the full cache for only 30 seconds ● app dir client cache semantics (30s/5min) › prefetch={undefined} - default › should renew the 30s cache once the data is revalidated ● app dir client cache semantics (30s/5min) › prefetch={undefined} - default › should refetch below the fold after 30 seconds ● app dir client cache semantics (30s/5min) › prefetch={undefined} - default › should refetch the full page after 5 mins ● app dir client cache semantics (30s/5min) › prefetch={undefined} - default › should respect a loading boundary that returns ● app dir client cache semantics (30s/5min) › should seed the prefetch cache with the fetched page data ● app dir client cache semantics (30s/5min) › should renew the initial seeded data after expiration time
Expand output● Custom Document Fragment Styles › production mode › correctly adds styles from fragment styles key
Expand output● app dir - middleware without pages dir › Updates headers
Expand output● devtools-position-top-right › should devtools indicator position initially be top-right when configured
Expand output● css-modules-pure-no-check › should apply styles correctly ● css-modules-pure-no-check › should have emitted a CSS file
Expand output● Configuration › should disable X-Powered-By header support ● Configuration › correctly imports a package that defines ● Configuration › should have env variables available on the client
Expand output● app dir - dynamic error trace › should show the error trace ● Test suite failed to run
Expand output● Catches Missing getStaticProps › production mode › should catch it in server build mode
Expand output● app-dir edge runtime root layout › should not emit metadata files into bad paths ● app-dir edge runtime root layout › should mark static contain metadata routes as edge functions
Expand output● RSC binary serialization › should correctly encode/decode binaries and hydrate ● RSC binary serialization › should correctly encode/decode binaries and hydrate
Expand output● next-config-ts-async-function-esm › should support config as async function (ESM)
Expand output● Export with getInitialProps › production mode › should show warning with next export
Expand output● CSS optimization for SSR apps › production mode › should have all CSS files in manifest ● CSS optimization for SSR apps › production mode › should inline critical CSS ● CSS optimization for SSR apps › production mode › should inline critical CSS (dynamic) ● CSS optimization for SSR apps › production mode › should not inline non-critical css
Expand output● app-dir - devtool-copy-button › should has inspect url copy button
Expand output● app dir - global-error - error-in-global-error › should be able to use nextjs navigation hook in global-error ● app dir - global-error - error-in-global-error › should render fallback UI when error occurs in global-error
Expand output● Default 404 Page with custom _error › development mode › should respond to 404 correctly ● Default 404 Page with custom _error › development mode › should render error correctly ● Default 404 Page with custom _error › development mode › should render index page normal
Expand output● actions-streaming › actions returning a ReadableStream › should properly stream the response without buffering
Expand output● dev indicator - Hide DevTools Button › should show the dev indicator when the server is manually restarted ● dev indicator - Hide DevTools Button › should still hide the dev indicator after reloading the page ● dev indicator - Hide DevTools Button › should show the dev indicator after cooldown period has passed
Expand output● next-config-ts-export-default-esm › should support export default (ESM)
Expand output● app dir rendering › should serve app/page.server.js at / ● app dir rendering › SSR only › should run data in layout and page ● app dir rendering › SSR only › should run data fetch in parallel ● app dir rendering › static only › should run data in layout and page ● app dir rendering › static only › should run data in parallel and use cached version for production ● app dir rendering › ISR › should revalidate the page when revalidate is configured ● app dir rendering › mixed static and dynamic › should generate static data during build and use it
Expand output● next-config-ts-export-default-cjs › should support export default (CJS)
Expand output● useDefineForClassFields SWC option › tsx should compile with useDefineForClassFields enabled ● useDefineForClassFields SWC option › Initializes resident to undefined after the call to 'super()' when with useDefineForClassFields enabled ● useDefineForClassFields SWC option › set accessors from base classes won’t get triggered with useDefineForClassFields enabled |
mischnic
force-pushed
the
mischnic/server-external-packages-jsonc
branch
from
4a6f07b to
355d7da
Compare
So that we can then use comments to track a reason why we have added packages to this list.