52c2f8b4dd
Next.js currently writes the TS type declarations on startup, regardless of the existing content of the file. This is good for ensuring the file content stays consistent. However, if the file content is already correct, this will perform an unnessecary write. When running Next in read-only filesystems (such as the Bazel sandbox) this can cause the build to fail even if the content of the type declaration file is already correct. This fixes this by only writing the contents of the file if the current contents don't match. ## Test Plan Added an integration test for the general behavior of writing `next-env.d.ts`. |
||
|---|---|---|
| .. | ||
| pages | ||
| test | ||
| next-env.d.ts | ||
| tsconfig.json | ||