Unverified Commit 5bd155e2 authored by Titus Moore's avatar Titus Moore Committed by GitHub

Added workaround for --isolatedModules inside of configuration files (#39004)


This relates to a bug from issue #38957 found inside of the `with-cypress` example as a result of the recent typescript conversion. This issue can be resolved with adding `export {};` which prevents TypeScript from reading `.ts` configuration files from being read as legacy script files. This issue has been resolved on StackOverflow [here](https://stackoverflow.com/questions/56577201/why-is-isolatedmodules-error-fixed-by-any-import). More info on `--isolatedModules` can be read [here](https://www.typescriptlang.org/tsconfig#isolatedModules).

## Bug

- [x] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [x] Errors have helpful link attached, see `contributing.md`


Fixes #38597
parent e2286eeb
......@@ -5,3 +5,6 @@ module.exports = defineConfig({
baseUrl: 'http://localhost:3000',
},
})
// Prevent TypeScript from reading file as legacy script
export {}
......@@ -18,3 +18,6 @@ describe('Navigation', () => {
cy.get('h1').contains('About Page')
})
})
// Prevent TypeScript from reading file as legacy script
export {}
......@@ -35,3 +35,6 @@
// }
// }
// }
// Prevent TypeScript from reading file as legacy script
export {}
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment