mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-09-28 21:24:26 +08:00
Jack Franklin
b6b062836c
In crrev.com/c/5629076 as a drive-by I included the root tsconfig in the interactions folder, but that was using a hammer to crack a nut and it caused some unexpected TypeScript errors in the interactions tests. The issue comes because unexpectedly we want to import from the front_end folder in the interaction tests - not normally done - and so you get a bunch of warnings in your editor (it does not impact the actual build). Extending the root tsconfig seems to cause confusion with TS and how it resolves some of the Puppeteer types so this CL localises the solution into just the performance/timeline folder and tells TS that it is OK to include files from the root front_end and test dir within there. Bug: none Change-Id: I3e923b1b9c874784ee3dd5bdfc9649abec696c79 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5822706 Auto-Submit: Jack Franklin <jacktfranklin@chromium.org> Commit-Queue: Jack Franklin <jacktfranklin@chromium.org> Reviewed-by: Simon Zünd <szuend@chromium.org> Commit-Queue: Simon Zünd <szuend@chromium.org>
19 lines
306 B
JSON
19 lines
306 B
JSON
{
|
|
"compilerOptions": {
|
|
"module": "commonjs",
|
|
"baseUrl": ".",
|
|
|
|
"checkJs": false,
|
|
"allowJs": false
|
|
},
|
|
"references": [
|
|
{
|
|
"path": "../shared/tsconfig.json"
|
|
},
|
|
{
|
|
"path": "../e2e/tsconfig.json"
|
|
},
|
|
],
|
|
"extends": "../../config/typescript/tsconfig.base.json"
|
|
}
|