Navalex

Same error with a basic Next.js setup. Jest is running good, but majestic just throw me a `ℹ Error occured while obtaining Jest cofiguration for coverage report SyntaxError: Unexpected token...

@jepiqueau sadly no, I'll first need to dive into TypeORM by itself (pretty new to SQLite). And i'm still not sure to go for sqlite storage, so it's paused for...

> When will this get merged? > > I'm using `prisma-json-schema-generator` to generate a json schema from my prisma file, but this file has definitions in it and at the...

Hello, any news on this case ? Does this PR just dropped because too complex too heavy with the current state of the library ? Or can we expect a...

@0xLLLLH still no updates on this PR ?

Yeah sorry, here is a little project I made up to reproduce this: `package.json` ```json { "name": "test", "version": "1.0.0", "main": "index.js", "scripts": { "test": "echo \"Error: no test specified\"...

Okay, I edited my schema: ```prisma generator client { provider = "prisma-client-js" } datasource db { provider = "sqlite" url = env("DATABASE_URL") } model User { name String @unique }...

> @navalex can you try with v[2.3.0-next.2](https://www.npmjs.com/package/ts-json-schema-generator/v/2.3.0-next.2)? > > After #1963 added diagnostics, the error thrown will have more info about it. Okay so, after testing, it does fix the...