question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

NoRootNamesError: No source files found

See original GitHub issue

I just updated from version 0.95.0 to 0.96.0 and the schema generator stopped working, I now get this message:

> ts-json-schema-generator -f tsconfig.json -t Foo > foo.schema.json

NoRootNamesError: No source files found

Can be reproduced with a minimal tsconfig.json (even one containing an empty object) and a simple export interface Foo { bar: string } type. Works with schema generator 0.95.0, but not with 0.96.0

Was there a change in the CLI parameters? I can’t find any entry in the changelog which sounds like a CLI change.

And maybe this issue is a good point to discuss the versioning of the the schema-generator. I’m using it for a long time now and I would say the interfaces for which I generate JSON schemas are very complex (Lots of generic types with many mapped types and conditional types for example). And since my last contributions to this project two years ago I never had a problem with it (well, until now). So in my opinion the schema generator is very stable and earns the right to get a production version number. After this the versioning should follow the semver paradigm and the major version number should be incremented when the public API (including the CLI parameters) is no longer compatible to the previous version.

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:8 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
vega-org-botcommented, Nov 4, 2021

🚀 Issue was released in v0.97.0 🚀

1reaction
kayahrcommented, Oct 7, 2021

Yes, #979 fixes the problem.

Read more comments on GitHub >

github_iconTop Results From Across the Web

node.js - Grunt warning: No source files found - Stack Overflow
The error means that grunt can't find the source files where you've specified that they should be. Are you sure the file exist...
Read more >
ts-json-schema-generator - npm
Generate JSON schema from your Typescript sources. ... the generated schema will contain all types found in the files matching path.
Read more >
[SOLVED] [Segger Ozone] - "No Source Files" found after .out ...
I am able to see function names, but not able to view any corresponding source files (The "source File" window displays "No Source...
Read more >
json-schema-to-typescript - npm package - Snyk
The npm package json-schema-to-typescript was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as ......
Read more >
no source files were specified" when Dockerfile is not in root ...
Coding example for the question "COPY failed: no source files were specified" when Dockerfile is not in root directory on Docker Hub-docker.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found