rsnext/packages/next
Jiachi Liu 8668020a54
Upgrade typescript to 4.8.2 (#39979)
Typescript published 4.8.2 today and it fails CI, bump our typescript version to 4.8.2 and tweak some typings to make existing e2e typescript tests work properly

* Bump web-vitals from 3.0.0-beta to 3.0.0 stable for typing fix (there's an undefined type but it wasn't caught by ts 4.7), also force compiled it as CJS for pre-compiled
* Bump ncc to 3.34.0 for ts-loader compatibility for new typescript version, ncc 3.33.x cannot work with ts 4.8
* Update pre-compiled
2022-08-29 16:56:02 +00:00
..
bin fix(next): dev server starting when importing a file using get-projec… (#38274) 2022-08-07 17:31:30 +00:00
build Handle async module for client components (#39953) 2022-08-29 14:47:06 +00:00
bundles Remove webpack4 types (#39631) 2022-08-16 09:55:37 +00:00
cli Enable @typescript-eslint/no-use-before-define for functions (#39602) 2022-08-15 10:29:51 -04:00
client Upgrade typescript to 4.8.2 (#39979) 2022-08-29 16:56:02 +00:00
compiled Upgrade typescript to 4.8.2 (#39979) 2022-08-29 16:56:02 +00:00
export Setup require hook in next-server for styled-jsx resolving (#39305) 2022-08-08 20:27:42 -05:00
future Add experimental next/future/image component (#37927) 2022-06-24 14:56:05 +00:00
image-types Don't import internally from types in next-env.d.ts (#34394) 2022-02-19 04:25:49 +01:00
lib Upgrade typescript to 4.8.2 (#39979) 2022-08-29 16:56:02 +00:00
pages Avoid bundling next/script in the server build by default (#40013) 2022-08-28 13:36:42 -05:00
server Upgrade typescript to 4.8.2 (#39979) 2022-08-29 16:56:02 +00:00
shared/lib Upgrade typescript to 4.8.2 (#39979) 2022-08-29 16:56:02 +00:00
telemetry Enable @typescript-eslint/no-use-before-define for functions (#39602) 2022-08-15 10:29:51 -04:00
trace Small code improvements (#37227) 2022-05-26 23:19:47 +00:00
types Enable additional TypeScript ESLint rules (#39640) 2022-08-16 11:08:40 +00:00
amp.d.ts
amp.js
app.d.ts
app.js
babel.d.ts
babel.js
client.d.ts
client.js
config.d.ts
config.js
constants.d.ts
constants.js
data.d.ts
data.js
data.sqlite
document.d.ts
document.js
dynamic.d.ts
dynamic.js
error.d.ts
error.js
head.d.ts
head.js fix(#36435): apply correct fix (#36464) 2022-04-26 11:15:49 -05:00
image.d.ts
image.js
index.d.ts typing: upgrade styled-jsx to remove workaround in build script (#39408) 2022-08-09 17:10:33 +00:00
jest.d.ts
jest.js fix(#36534): enable interopClientDefaultExport for next/jest (#36824) 2022-05-11 13:13:13 -05:00
license.md
link.d.ts
link.js
package.json Upgrade typescript to 4.8.2 (#39979) 2022-08-29 16:56:02 +00:00
README.md Update README.md (#38371) 2022-07-07 23:00:34 -05:00
router.d.ts
router.js
script.d.ts
script.js
server.d.ts Export URLPattern from next/server (#39219) 2022-08-02 02:04:08 +00:00
server.js refactor: add named export in next/server (#39381) 2022-08-07 16:17:15 +00:00
taskfile-ncc.js
taskfile-swc.js chore: enable swc externalHelpers when pre-compile (#38182) 2022-07-26 14:23:19 -05:00
taskfile.js Upgrade typescript to 4.8.2 (#39979) 2022-08-29 16:56:02 +00:00
tsconfig.json Remove webpack4 types (#39631) 2022-08-16 09:55:37 +00:00

Next.js

Getting Started

Visit https://nextjs.org/learn to get started with Next.js.

Documentation

Visit https://nextjs.org/docs to view the full documentation.

Who is using Next.js?

Next.js is used by the world's leading companies. Check out the Next.js Showcase to learn more.

Community

The Next.js community can be found on GitHub Discussions, where you can ask questions, voice ideas, and share your projects.

To chat with other community members you can join the Next.js Discord.

Our Code of Conduct applies to all Next.js community channels.

Contributing

Please see our contributing.md.

Good First Issues

We have a list of good first issues that contain bugs which have a relatively limited scope. This is a great place to get started, gain experience, and get familiar with our contribution process.

Authors

Security

If you believe you have found a security vulnerability in Next.js, we encourage you to responsibly disclose this and not open a public issue. We will investigate all legitimate reports. Email security@vercel.com to disclose any security vulnerabilities.

https://vercel.com/security