rsnext/packages/third-parties/tsconfig.json

{
  "compilerOptions": {
    "strict": true,
    "esModuleInterop": true,
    "target": "es2019",
    "outDir": "dist",
    "jsx": "react",
    "resolveJsonModule": true,
    "module": "commonjs",
    "rootDir": "src"
  },
  "include": ["src/**/*.ts", "src/**/*.tsx"],
  "exclude": ["node_modules"]
}
Setting up third-parties package (#51194) This PR Introduces `next/third-parties` - `@next/third-parties` is a new package in the Next.js monorepo. - The package contains collection of components that can be used to efficiently load third party libraries into your Next.js application. - This package uses [Third Party Capital](https://github.com/GoogleChromeLabs/third-party-capital/) under the hood to fetch the best loading recommendations. - This PR mainly sets up the package to run a script at build time to auto generate the components from [Third Party Capital](https://github.com/GoogleChromeLabs/third-party-capital/) config. Packages are grouped by company, for eg: `import { GoogleMapsEmbed } from '@next/third-parties/google'` cc: @housseindjirdeh @kara <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # --> --------- 2023-07-18 19:52:39 +02:00			`{`
			`"compilerOptions": {`
			`"strict": true,`
			`"esModuleInterop": true,`
Adding GoogleMaps and Youtube embed components (#52909) Adding GoogleMapsEmbed and YoutubeEmber components into `@next/third-parties` Adding tests and README Each component is tagged with `data-ntpc` attribute cc: @kara @housseindjirdeh @huozhi @gnoff Co-authored-by: Jiachi Liu <4800338+huozhi@users.noreply.github.com> 2023-08-07 21:38:13 +02:00			`"target": "es2019",`
Setting up third-parties package (#51194) This PR Introduces `next/third-parties` - `@next/third-parties` is a new package in the Next.js monorepo. - The package contains collection of components that can be used to efficiently load third party libraries into your Next.js application. - This package uses [Third Party Capital](https://github.com/GoogleChromeLabs/third-party-capital/) under the hood to fetch the best loading recommendations. - This PR mainly sets up the package to run a script at build time to auto generate the components from [Third Party Capital](https://github.com/GoogleChromeLabs/third-party-capital/) config. Packages are grouped by company, for eg: `import { GoogleMapsEmbed } from '@next/third-parties/google'` cc: @housseindjirdeh @kara <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # --> --------- 2023-07-18 19:52:39 +02:00			`"outDir": "dist",`
			`"jsx": "react",`
Adding GoogleMaps and Youtube embed components (#52909) Adding GoogleMapsEmbed and YoutubeEmber components into `@next/third-parties` Adding tests and README Each component is tagged with `data-ntpc` attribute cc: @kara @housseindjirdeh @huozhi @gnoff Co-authored-by: Jiachi Liu <4800338+huozhi@users.noreply.github.com> 2023-08-07 21:38:13 +02:00			`"resolveJsonModule": true,`
			`"module": "commonjs",`
			`"rootDir": "src"`
Setting up third-parties package (#51194) This PR Introduces `next/third-parties` - `@next/third-parties` is a new package in the Next.js monorepo. - The package contains collection of components that can be used to efficiently load third party libraries into your Next.js application. - This package uses [Third Party Capital](https://github.com/GoogleChromeLabs/third-party-capital/) under the hood to fetch the best loading recommendations. - This PR mainly sets up the package to run a script at build time to auto generate the components from [Third Party Capital](https://github.com/GoogleChromeLabs/third-party-capital/) config. Packages are grouped by company, for eg: `import { GoogleMapsEmbed } from '@next/third-parties/google'` cc: @housseindjirdeh @kara <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # --> --------- 2023-07-18 19:52:39 +02:00			`},`
			`"include": ["src/*/.ts", "src/*/.tsx"],`
			`"exclude": ["node_modules"]`
			`}`