-
Notifications
You must be signed in to change notification settings - Fork 26.8k
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.
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
Update devdependecy conf nextjs #67140
base: canary
Are you sure you want to change the base?
Update devdependecy conf nextjs #67140
Conversation
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/conf@5.0.0, npm/postcss-scss@4.0.3 |
@samcx I have done the PR of |
@samcx As a step in |
Failing test suitesCommit: d3ca6a2
Expand output● App asPath › should not have any changes in asPath after a bundle rebuild
Read more about building and testing Next.js in contributing.md. |
Failing test suitesCommit: bfe71a3
Expand output● 500 Page Support › development mode › should use pages/500
● 500 Page Support › development mode › should set correct status code with pages/500
● 500 Page Support › development mode › should not error when visited directly
● 500 Page Support › development mode 2 › shows error with getInitialProps in pages/500 dev
Read more about building and testing Next.js in contributing.md.
Expand output● App asPath › should not have any changes in asPath after a bundle rebuild
Read more about building and testing Next.js in contributing.md.
Expand output● gsp-gssp › development mode › does not show error with getStaticProps in pages/500 dev
● gsp-gssp › development mode › shows error with getServerSideProps in pages/500 dev
Read more about building and testing Next.js in contributing.md.
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 not show an error in the logs for 404 SSG
● 404 Page Support SSG › development mode › should render index page normal
Read more about building and testing Next.js in contributing.md.
Expand output● 404 Page Support › development mode › should use pages/404
● 404 Page Support › development mode › should set correct status code with pages/404
● 404 Page Support › development mode › should use pages/404 for .d.ts file
● 404 Page Support › development mode › should not error when visited directly
● 404 Page Support › development mode › should render _error for a 500 error still
● 404 Page Support › development mode 2 › falls back to _error correctly without pages/404
● 404 Page Support › development mode 2 › shows error with getInitialProps in pages/404 dev
● 404 Page Support › development mode 2 › does not show error with getStaticProps in pages/404 dev
● 404 Page Support › development mode 2 › shows error with getServerSideProps in pages/404 dev
Read more about building and testing Next.js in contributing.md.
Expand output● app-prefetch-static › should correctly navigate between static & dynamic pages
Read more about building and testing Next.js in contributing.md.
Expand output● app-dynamic-error › production mode › throws an error when prerendering a page with config dynamic error
Read more about building and testing Next.js in contributing.md.
Expand output● AMP Fragment Styles › production mode › adds styles from fragment in AMP mode correctly
Read more about building and testing Next.js in contributing.md.
Expand output● Test suite failed to run
Read more about building and testing Next.js in contributing.md.
Expand output● Promise in next config › production mode › should warn when a promise is returned on webpack
Read more about building and testing Next.js in contributing.md.
Expand output● app dir › Loading › should render loading.js in initial html for slow page
Read more about building and testing Next.js in contributing.md.
Expand output● build trace with extra entries › production mode › should build and trace correctly
Read more about building and testing Next.js in contributing.md.
Expand output● app-dir edge SSR › should handle edge only routes
● app-dir edge SSR › should retrieve cookies in a server component in the edge runtime
● app-dir edge SSR › should treat process as object without polyfill in edge runtime
● app-dir edge SSR › should handle /index routes correctly
● app-dir edge SSR › should generate matchers correctly in middleware manifest
Read more about building and testing Next.js in contributing.md.
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
Read more about building and testing Next.js in contributing.md.
Expand output● app-routes-subrequests › shortcuts after 5 subrequests
Read more about building and testing Next.js in contributing.md.
Expand output● Default 404 Page with custom _error › production mode › should build successfully
● Default 404 Page with custom _error › production mode › should respond to 404 correctly
● Default 404 Page with custom _error › production mode › should render error correctly
● Default 404 Page with custom _error › production mode › should render index page normal
● Default 404 Page with custom _error › production mode › should set pages404 in routes-manifest correctly
● Default 404 Page with custom _error › production mode › should have output 404.html
Read more about building and testing Next.js in contributing.md.
Expand output● app a11y features › route announcer › should not announce the initital title
● app a11y features › route announcer › should announce document.title changes
● app a11y features › route announcer › should announce h1 changes
● app a11y features › route announcer › should announce route changes when h1 changes inside an inner layout
Read more about building and testing Next.js in contributing.md.
Expand output● app dir - validation › should error when passing invalid router state tree
Read more about building and testing Next.js in contributing.md.
Expand output● app dir - dynamic error trace › should show the error trace
● Test suite failed to run
Read more about building and testing Next.js in contributing.md.
Expand output● Undefined default export › should error if page component does not have default export
● Undefined default export › should error if not-found component does not have default export when trigger not-found boundary
● Undefined default export › should error when page component export is not valid
● Undefined default export › should error when page component export is not valid on initial load
● Test suite failed to run
Read more about building and testing Next.js in contributing.md.
Expand output● Error overlay - RSC runtime errors › should show runtime errors if invalid client API from node_modules is executed
● Error overlay - RSC runtime errors › should show runtime errors if invalid server API from node_modules is executed
● Error overlay - RSC runtime errors › should show source code for jsx errors from server component
● Error overlay - RSC runtime errors › should show the userland code error trace when fetch failed error occurred
● Error overlay - RSC runtime errors › should contain nextjs version check in error overlay
● Error overlay - RSC runtime errors › should not show the bundle layer info in the file trace
● Test suite failed to run
Read more about building and testing Next.js in contributing.md. |
@torresgol10 It looks like the |
@samcx It's weird, I ran the build and everything worked, I'll investigate what happened and figure out how to fix it. |
@samcx Sorry about that. Right now I don't know how to fix it, I found that it fails in the tests not in the build and it fails in the I don't know, if you could help me |
Bump devDependecy
Conf
to 13.0.1