You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
IntelliSense slow down with large json file #48364
Does this issue occur when all extensions are disabled?: Yes
VS Code Version: 1.65.2
OS Version: Ubuntu 20.04.4 LTS
IntelliSense slow down when I set value for compilerOptions->jsx option in tsconfig.json file. Without this option (after restart vscode) I get autocomplete suggestion less then 1 second, with compilerOptions->jsx I get suggestion after 3-4 seconds. CPU i5 8 cores, available RAM more than 10GB.
When initializing js/ts language features in progress IntelliSense work fast
I'm having the same problem (M1 Mac) and I tried the Bisect tool without any success. Can't share my project but I can share my tsconfig:
"compilerOptions": {
/* Visit https://aka.ms/tsconfig.json to read more about this file */
/* Projects */
// "incremental": true, /* Enable incremental compilation */
// "composite": true, /* Enable constraints that allow a TypeScript project to be used with project references. */
// "tsBuildInfoFile": "./", /* Specify the folder for .tsbuildinfo incremental compilation files. */
// "disableSourceOfProjectReferenceRedirect": true, /* Disable preferring source files instead of declaration files when referencing composite projects */
// "disableSolutionSearching": true, /* Opt a project out of multi-project reference checking when editing. */
// "disableReferencedProjectLoad": true, /* Reduce the number of projects loaded automatically by TypeScript. */
/* Language and Environment */
"target": "ESNext", /* Set the JavaScript language version for emitted JavaScript and include compatible library declarations. */
// "lib": [], /* Specify a set of bundled library declaration files that describe the target runtime environment. */
// "jsx": "preserve", /* Specify what JSX code is generated. */
// "experimentalDecorators": true, /* Enable experimental support for TC39 stage 2 draft decorators. */
// "emitDecoratorMetadata": true, /* Emit design-type metadata for decorated declarations in source files. */
// "jsxFactory": "", /* Specify the JSX factory function used when targeting React JSX emit, e.g. 'React.createElement' or 'h' */
// "jsxFragmentFactory": "", /* Specify the JSX Fragment reference used for fragments when targeting React JSX emit e.g. 'React.Fragment' or 'Fragment'. */
// "jsxImportSource": "", /* Specify module specifier used to import the JSX factory functions when using `jsx: react-jsx*`.` */
// "reactNamespace": "", /* Specify the object invoked for `createElement`. This only applies when targeting `react` JSX emit. */
// "noLib": true, /* Disable including any library files, including the default lib.d.ts. */
// "useDefineForClassFields": true, /* Emit ECMAScript-standard-compliant class fields. */
/* Modules */
"module": "ESNext", /* Specify what module code is generated. */
// "rootDir": "./", /* Specify the root folder within your source files. */
"moduleResolution": "node", /* Specify how TypeScript looks up a file from a given module specifier. */
// "baseUrl": "./", /* Specify the base directory to resolve non-relative module names. */
// "paths": {}, /* Specify a set of entries that re-map imports to additional lookup locations. */
// "rootDirs": [], /* Allow multiple folders to be treated as one when resolving modules. */
// "typeRoots": [], /* Specify multiple folders that act like `./node_modules/@types`. */
// "types": [], /* Specify type package names to be included without being referenced in a source file. */
// "allowUmdGlobalAccess": true, /* Allow accessing UMD globals from modules. */
"resolveJsonModule": true, /* Enable importing .json files */
// "noResolve": true, /* Disallow `import`s, `require`s or `<reference>`s from expanding the number of files TypeScript should add to a project. */
/* JavaScript Support */
"allowJs": true, /* Allow JavaScript files to be a part of your program. Use the `checkJS` option to get errors from these files. */
// "checkJs": true, /* Enable error reporting in type-checked JavaScript files. */
// "maxNodeModuleJsDepth": 1, /* Specify the maximum folder depth used for checking JavaScript files from `node_modules`. Only applicable with `allowJs`. */
/* Emit */
// "declaration": true, /* Generate .d.ts files from TypeScript and JavaScript files in your project. */
// "declarationMap": true, /* Create sourcemaps for d.ts files. */
// "emitDeclarationOnly": true, /* Only output d.ts files and not JavaScript files. */
"sourceMap": true, /* Create source map files for emitted JavaScript files. */
// "outFile": "./", /* Specify a file that bundles all outputs into one JavaScript file. If `declaration` is true, also designates a file that bundles all .d.ts output. */
"outDir": "./built", /* Specify an output folder for all emitted files. */
// "removeComments": true, /* Disable emitting comments. */
// "noEmit": true, /* Disable emitting files from a compilation. */
// "importHelpers": true, /* Allow importing helper functions from tslib once per project, instead of including them per-file. */
// "importsNotUsedAsValues": "remove", /* Specify emit/checking behavior for imports that are only used for types */
// "downlevelIteration": true, /* Emit more compliant, but verbose and less performant JavaScript for iteration. */
// "sourceRoot": "", /* Specify the root path for debuggers to find the reference source code. */
// "mapRoot": "", /* Specify the location where debugger should locate map files instead of generated locations. */
// "inlineSourceMap": true, /* Include sourcemap files inside the emitted JavaScript. */
// "inlineSources": true, /* Include source code in the sourcemaps inside the emitted JavaScript. */
// "emitBOM": true, /* Emit a UTF-8 Byte Order Mark (BOM) in the beginning of output files. */
// "newLine": "crlf", /* Set the newline character for emitting files. */
// "stripInternal": true, /* Disable emitting declarations that have `@internal` in their JSDoc comments. */
// "noEmitHelpers": true, /* Disable generating custom helper functions like `__extends` in compiled output. */
// "noEmitOnError": true, /* Disable emitting files if any type checking errors are reported. */
// "preserveConstEnums": true, /* Disable erasing `const enum` declarations in generated code. */
// "declarationDir": "./", /* Specify the output directory for generated declaration files. */
// "preserveValueImports": true, /* Preserve unused imported values in the JavaScript output that would otherwise be removed. */
/* Interop Constraints */
// "isolatedModules": true, /* Ensure that each file can be safely transpiled without relying on other imports. */
// "allowSyntheticDefaultImports": true, /* Allow 'import x from y' when a module doesn't have a default export. */
"esModuleInterop": true, /* Emit additional JavaScript to ease support for importing CommonJS modules. This enables `allowSyntheticDefaultImports` for type compatibility. */
// "preserveSymlinks": true, /* Disable resolving symlinks to their realpath. This correlates to the same flag in node. */
"forceConsistentCasingInFileNames": true, /* Ensure that casing is correct in imports. */
/* Type Checking */
"strict": true, /* Enable all strict type-checking options. */
// "noImplicitAny": true, /* Enable error reporting for expressions and declarations with an implied `any` type.. */
// "strictNullChecks": true, /* When type checking, take into account `null` and `undefined`. */
// "strictFunctionTypes": true, /* When assigning functions, check to ensure parameters and the return values are subtype-compatible. */
// "strictBindCallApply": true, /* Check that the arguments for `bind`, `call`, and `apply` methods match the original function. */
// "strictPropertyInitialization": true, /* Check for class properties that are declared but not set in the constructor. */
// "noImplicitThis": true, /* Enable error reporting when `this` is given the type `any`. */
// "useUnknownInCatchVariables": true, /* Type catch clause variables as 'unknown' instead of 'any'. */
// "alwaysStrict": true, /* Ensure 'use strict' is always emitted. */
// "noUnusedLocals": true, /* Enable error reporting when a local variables aren't read. */
// "noUnusedParameters": true, /* Raise an error when a function parameter isn't read */
// "exactOptionalPropertyTypes": true, /* Interpret optional property types as written, rather than adding 'undefined'. */
// "noImplicitReturns": true, /* Enable error reporting for codepaths that do not explicitly return in a function. */
// "noFallthroughCasesInSwitch": true, /* Enable error reporting for fallthrough cases in switch statements. */
// "noUncheckedIndexedAccess": true, /* Include 'undefined' in index signature results */
// "noImplicitOverride": true, /* Ensure overriding members in derived classes are marked with an override modifier. */
// "noPropertyAccessFromIndexSignature": true, /* Enforces using indexed accessors for keys declared using an indexed type */
// "allowUnusedLabels": true, /* Disable error reporting for unused labels. */
// "allowUnreachableCode": true, /* Disable error reporting for unreachable code. */
/* Completeness */
// "skipDefaultLibCheck": true, /* Skip type checking .d.ts files that are included with TypeScript. */
"skipLibCheck": true /* Skip type checking all .d.ts files. */
},
"exclude": [
"node_modules",
".npm"
],
"include": ["./src"]
}
Can't share project too. I found tsx file with a lot of imports (49), if some of imports are commented then all works fine. Tried to find root of issue but this imports has another imports, they has another and etc. I solved this problem by downgrading to the previous version of vscode (1.64.2)
Steve Ross (@steve-ross) Can you share the json file that causes the problem (feel free to turn the actual contents into gibberish as long as it still demonstrates the issue)
Matt Bierner (@mjbvz) I'll work on getting you a file I can send your way. In the current state I can't send it due to customer data being in the file.
Matt Bierner (@mjbvz) here's one of my json files... pretty big file (had 2 more I was also importing that were 1.5mb each. Pretty sure I noticed the issue with just one though. Attached is my tsconfig and sample json.
steve-ross in the future can you please make sure to open a new issue when reporting problems. I just assumed you were the OP but I think you're talking about a different problem than what sublite originally reported
sublite If you're seeing the original problem, please share a project that demonstrates the issue
Update on this bug: I've looked into making type checking array literals faster, but it doesn't look like this would be enough to solve the intellisense slowdown for the examples listed here.
Instead, what I suggest as a fix is the following:
If you're importing a large JSON (array) module with resolveJsonModule set, and you're experiencing slow intellisense in the file(s) that imports this JSON (e.g. slow completions, slow updates to errors/red squiggles, etc), you can set our new flag "allowArbitraryExtensions": true on your tsconfig's compilerOptions, and write a .d.json.ts file with the type of your JSON module.
Example: index.ts:
importxfrom'./myJson.json';x[0];// { prop: number }
Then, when importing the JSON, TS will get the types from your .d.json.ts file instead of type checking the JSON every time your file changes in the editor, making it way faster.
The allowArbitraryExtensions flag is currently only present on the nightly versions, but it will be officially available starting at the 5.0 beta version that we'll release in the next couple weeks.
Reacted by Lucas Fisher, KoheiKanagu, Variant9, Gavin Acquroff, noemica, 🔰kasima(t) and JameyPlay
Reacted by Lucas Fisher, Javi Aguilar, Gavin Acquroff and Junyang
Experiencing this too. To fix it just added //@ts-ignore above the .json import. I dont want to type the .json so for me its ok to just ignore. On my project I just replicated the structure of the types and thats enough for whenever im using this data
Activity
mjbvz commentedon Mar 14, 2022
Can you share a project that demonstrates the issue?
steve-ross commentedon Mar 16, 2022
I'm having the same problem (M1 Mac) and I tried the Bisect tool without any success. Can't share my project but I can share my tsconfig:
steve-ross commentedon Mar 16, 2022
Wellp... fixed by setting "resolveJsonModule": false... guess it's my import of some huge json files that is causing the issue.
sublite commentedon Mar 17, 2022
Can't share project too. I found tsx file with a lot of imports (49), if some of imports are commented then all works fine. Tried to find root of issue but this imports has another imports, they has another and etc. I solved this problem by downgrading to the previous version of vscode (1.64.2)
mjbvz commentedon Mar 17, 2022
Steve Ross (@steve-ross) Can you share the json file that causes the problem (feel free to turn the actual contents into gibberish as long as it still demonstrates the issue)
steve-ross commentedon Mar 17, 2022
Matt Bierner (@mjbvz) I'll work on getting you a file I can send your way. In the current state I can't send it due to customer data being in the file.
steve-ross commentedon Mar 21, 2022
Matt Bierner (@mjbvz) here's one of my json files... pretty big file (had 2 more I was also importing that were 1.5mb each. Pretty sure I noticed the issue with just one though. Attached is my tsconfig and sample json.
Vscode about:
sample-file-and-config.zip
[-]IntelliSense slow down with tsconfig setting[/-][+]IntelliSense slow down with large json file[/+]mjbvz commentedon Mar 21, 2022
Thanks Steve Ross (@steve-ross)
Relevant TS Server log from a JS file that imports that large json file:
tsserver.log
I see a ~1 second delay here. Here's what I believe is the relevant request:
This delay happens every time I edit the document and trigger suggestions
mjbvz commentedon Mar 21, 2022
steve-ross in the future can you please make sure to open a new issue when reporting problems. I just assumed you were the OP but I think you're talking about a different problem than what sublite originally reported
sublite If you're seeing the original problem, please share a project that demonstrates the issue
10 remaining items
ryancwalsh commentedon Oct 19, 2022
Gabriela Araujo Britto (@gabritto) https://github.com/ryancwalsh/paint_color_gallery/blob/main/data/colornerd.json
gabritto commentedon Jan 16, 2023
Update on this bug: I've looked into making type checking array literals faster, but it doesn't look like this would be enough to solve the intellisense slowdown for the examples listed here.
Instead, what I suggest as a fix is the following:
If you're importing a large JSON (array) module with
resolveJsonModuleset, and you're experiencing slow intellisense in the file(s) that imports this JSON (e.g. slow completions, slow updates to errors/red squiggles, etc), you can set our new flag"allowArbitraryExtensions": trueon your tsconfig'scompilerOptions, and write a.d.json.tsfile with the type of your JSON module.Example:
index.ts:myJson.json:[{ "prop": 1 }]myJson.d.json.ts:Then, when importing the JSON, TS will get the types from your
.d.json.tsfile instead of type checking the JSON every time your file changes in the editor, making it way faster.The
allowArbitraryExtensionsflag is currently only present on the nightly versions, but it will be officially available starting at the 5.0 beta version that we'll release in the next couple weeks.ryancwalsh commentedon Jan 16, 2023
Gabriela Araujo Britto (@gabritto) I appreciate it. I will check that out next time.
lsfisher commentedon Mar 2, 2023
Gabriela Araujo Britto (@gabritto) thanks this was immensely helpful
Feat: Add typed json mock import (#3565)
ditorodev commentedon Aug 23, 2024
Experiencing this too. To fix it just added
//@ts-ignoreabove the .json import. I dont want to type the.jsonso for me its ok to just ignore. On my project I just replicated the structure of the types and thats enough for whenever im using this dataDedupe identical object literal types before subtype reduction