I'm trying to add lottie animation in my project and even if I provided the option to resolve json file, compilation process keeps failing saying that I need to enable the option.
Here my tsconfig:
{ "compilerOptions": { "module": "esnext", "target": "esnext", // We're bundling all code in the end so this is the most appropriate option, // it's also important for autocomplete to work properly. "moduleResolution": "node", // JSX support "jsx": "preserve", "strict": true, // Allow default imports. "esModuleInterop": true, "resolveJsonModule": true, "lib": [ "dom", "dom.iterable", "esnext" ], "allowJs": true, "typeRoots": [ // This is needed to properly support Vitest testing with jest-dom matchers. // Types for jest-dom are not recognized automatically and Typescript complains // about missing types e.g. when using `toBeInTheDocument` and other matchers. "node_modules/@testing-library", // Specifying type roots overrides the default behavior of looking at the // node_modules/@types folder so we had to list it explicitly. // Source 1: https://www.typescriptlang.org/tsconfig#typeRoots // Source 2: https://github.com/testing-library/jest-dom/issues/546#issuecomment-1889884843 "node_modules/@types" ], // Since this TS config is used only for IDE support and not for // compilation, the following directory doesn't exist. We need to specify // it to prevent this error: // https://stackoverflow.com/questions/42609768/typescript-error-cannot-write-file-because-it-would-overwrite-input-file "outDir": ".wasp/phantom" }}
{ "compilerOptions": { "module": "esnext", "target": "esnext", // We're bundling all code in the end so this is the most appropriate option, // it's also important for autocomplete to work properly. "moduleResolution": "node", // JSX support "jsx": "preserve", "strict": true, // Allow default imports. "esModuleInterop": true, "resolveJsonModule": true, "lib": [ "dom", "dom.iterable", "esnext" ], "allowJs": true, "typeRoots": [ // This is needed to properly support Vitest testing with jest-dom matchers. // Types for jest-dom are not recognized automatically and Typescript complains // about missing types e.g. when using `toBeInTheDocument` and other matchers. "node_modules/@testing-library", // Specifying type roots overrides the default behavior of looking at the // node_modules/@types folder so we had to list it explicitly. // Source 1: https://www.typescriptlang.org/tsconfig#typeRoots // Source 2: https://github.com/testing-library/jest-dom/issues/546#issuecomment-1889884843 "node_modules/@types" ], // Since this TS config is used only for IDE support and not for // compilation, the following directory doesn't exist. We need to specify // it to prevent this error: // https://stackoverflow.com/questions/42609768/typescript-error-cannot-write-file-because-it-would-overwrite-input-file "outDir": ".wasp/phantom" }}
Recent Announcements
Continue the conversation
Join the Discord to ask follow-up questions and connect with the community
W
Wasp
Rails-like framework for React, Node.js and Prisma. Build your app in a day and deploy it with a single CLI command.