Generated `tsconfig.json` is not `json` compliant
See original GitHub issueWhen generating the tsconfig.json
avoid any comment because IDE can complain about it.
Original report was in forum: https://vaadin.com/forum/thread/18187819/problem-vaadin-15-0-3-and-eclipse
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (1 by maintainers)
Top Results From Across the Web
Generated `tsconfig.json` is not `json` compliant · Issue #325
A tsconfig.json file in a Vaadin 14.1.27 app? That sounds very confusing to me as I am pretty confident Vaadin 14.x does not...
Read more >tsconfig.json: not input were found in config file?
1 Answer 1 ... It probably means that the Typescript compiler is unable to find your source files. You can add an include...
Read more >Documentation - What is a tsconfig.json - TypeScript
The tsconfig. json file specifies the root files and the compiler options required to compile the project. JavaScript projects can use a jsconfig....
Read more >Using TypeScript - Expo Documentation
To get started, create a tsconfig.json in your project root: Terminal ... If the file did not include any JSX, you can use...
Read more >typescript-json-schema - npm
typescript -json-schema generates JSON Schema files from your Typescript sources. ... In case no tsconfig.json is available for your project, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yes you can configure eclipse not to run the json analysis for a project. Add exclude group and then add the rule. (Be sure the rule says ‘folder’ and not ‘file’)
Still it would be nice if there is no json problem at all.
Thanks! Now I understand the issue better. The screenshot shows that Eclipse complains about a file deep inside the
node_modules
folder. While this is not in direct control of Vaadin (it comes from a dependency and we do not generate this file nor can we modify it), I see how this becomes an annoying issue when you work with a Vaadin project in Eclipse.I wonder, is there a way to configure Eclipse to not run any analysis on the contents of the
node_modules
folder.