tldraw/templates/nextjs/next.config.cjs

/** @type {import('next').NextConfig} */
const nextConfig = {
	experimental: {
		serverComponentsExternalPackages: ['@tldraw/tldraw'],
	},
}

module.exports = nextConfig
Use github actions to mirror templates from monorepo to appropriate repos (#2781) The idea here is to mirror project templates from our monorepo to the corresponding "top level" repos in our organisation. The main benefits are: - being able to easily synchronise template versions to the last release on release - being able to test those templates together with the rest of the project - being able to deploy the unreleased version of the templates However, this PR will only do the synchronisation part. The main roadblock for the latter at the moment is running `yarn install` on packages in the current `main` that are still unreleased. There are ways around that, but this PR is deliberately minimalistic to land it sooner. ### Change Type - [x] `internal` — Any other changes that don't affect the published package --------- Co-authored-by: Taha <98838967+Taha-Hassan-Git@users.noreply.github.com> 2024-02-29 10:48:31 +00:00			`/** @type {import('next').NextConfig} */`
			`const nextConfig = {`
[dx] Allow vscode to search inside md files by default (#3105) Before this PR all .md files were targeted by the `.ignore` file, which has bitten me on a number of occasions since .md files often contain valuable information (e.g. the vscode extensions docs). This PR unignores .md files while still ignoring _generated_ .md files like our changelogs, the api-report files, and the generated docs sections. Additionally, the `yarn format` and `yarn lint` commands were configured slightly differently, which was confusing, so I've unified those and simplified the lint.ts script at the same time. ### Change Type - [ ] `patch` — Bug fix - [ ] `minor` — New feature - [ ] `major` — Breaking change - [ ] `dependencies` — Changes to package dependencies[^1] - [ ] `documentation` — Changes to the documentation only[^2] - [ ] `tests` — Changes to any test code only[^2] - [x] `internal` — Any other changes that don't affect the published package[^2] - [ ] I don't know [^1]: publishes a `patch` release, for devDependencies use `internal` [^2]: will not publish a new version 2024-03-11 14:08:04 +00:00			`experimental: {`
			`serverComponentsExternalPackages: ['@tldraw/tldraw'],`
			`},`
			`}`
Use github actions to mirror templates from monorepo to appropriate repos (#2781) The idea here is to mirror project templates from our monorepo to the corresponding "top level" repos in our organisation. The main benefits are: - being able to easily synchronise template versions to the last release on release - being able to test those templates together with the rest of the project - being able to deploy the unreleased version of the templates However, this PR will only do the synchronisation part. The main roadblock for the latter at the moment is running `yarn install` on packages in the current `main` that are still unreleased. There are ways around that, but this PR is deliberately minimalistic to land it sooner. ### Change Type - [x] `internal` — Any other changes that don't affect the published package --------- Co-authored-by: Taha <98838967+Taha-Hassan-Git@users.noreply.github.com> 2024-02-29 10:48:31 +00:00
[dx] Allow vscode to search inside md files by default (#3105) Before this PR all .md files were targeted by the `.ignore` file, which has bitten me on a number of occasions since .md files often contain valuable information (e.g. the vscode extensions docs). This PR unignores .md files while still ignoring _generated_ .md files like our changelogs, the api-report files, and the generated docs sections. Additionally, the `yarn format` and `yarn lint` commands were configured slightly differently, which was confusing, so I've unified those and simplified the lint.ts script at the same time. ### Change Type - [ ] `patch` — Bug fix - [ ] `minor` — New feature - [ ] `major` — Breaking change - [ ] `dependencies` — Changes to package dependencies[^1] - [ ] `documentation` — Changes to the documentation only[^2] - [ ] `tests` — Changes to any test code only[^2] - [x] `internal` — Any other changes that don't affect the published package[^2] - [ ] I don't know [^1]: publishes a `patch` release, for devDependencies use `internal` [^2]: will not publish a new version 2024-03-11 14:08:04 +00:00			`module.exports = nextConfig`