tsdx | Zero-config CLI for TypeScript package development | Frontend Framework library

I'm new to Node and In this package.json for React Typescript project I understand what rimraf does but what is the --tsconfig doing at the end?

When I run the prebuild script I see that the file typedoc.json is deleted. But why this --tsconfig? There is a tsconfig.json file but I can’t see that rimraf is doing anything

I have the following problem and know exactly why it has been triggered, but I haven't found any solution yet, so probably the community may help me with that.

I am using tsdx for initiating ts repos, and also ts-node for quick debug (instead of building code each time).

So, each time when I want to add the module to my package via yarn add modulename and if in my tsconfig.json file in compilerOptions option: "module": "commonjs" has the following value, tsdx build unable to build code, and return me the following error:

Error: Incompatible tsconfig option. Module resolves to 'CommonJS'. This is incompatible with rollup, please use 'module: "ES2015"' or 'module: "ESNext"'

BUT!

if I will update compilerOptions to module: "ESNext" from commonjs, ts-node will give me an error, because it's still unable to use import {Method} from Module instead of const x = require(CommonJS) (which is quite old bug, according to this issue and this question)

• Typescript -v 4.1.5 (latest)
• ts-node: "^9.1.1"
• node -v: 15+

I created a npm package using TSdx for a small Jest reporter. If I use that package in another project, I get the following error.

I'm using Prisma upsert and getting an error about missing a required value when I'm trying to set one of the fields, which is an array type, specifically numeric[].

I'm using Prisma version 2.6.0

Data is getting into the database for all except a handful of rows and I'm getting an error thrown by Prisma on those rows when the upsert executes.

The error I'm getting from prisma is related to the array I'm trying to set:

I have created a React library using TSDX → https://github.com/deadcoder0904/react-typical

It uses CSS Modules & attaches styles to the React library.

The bundle correctly outputs CSS file into the dist/ folder but it never really references it as it should.

This causes my styles to not show up at all.

Here's my complete tsdx.config.js:

I have made a React library using https://tsdx.io & chose the React + TypeScript + Storybook template.

The entire code is here → https://github.com/deadcoder0904/react-typical

I get this error:

undefined is not iterable (cannot read property Symbol(Symbol.iterator)) TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator)) at __read (http://localhost:6006/vendors~main.c9781e3a7458a3b52f4d.bundle.js:177373:46) at __spread (http://localhost:6006/vendors~main.c9781e3a7458a3b52f4d.bundle.js:177391:24) at http://localhost:6006/main.c9781e3a7458a3b52f4d.bundle.js:77:127 at commitHookEffectListMount (http://localhost:6006/vendors~main.c9781e3a7458a3b52f4d.bundle.js:140995:26) at commitPassiveHookEffects (http://localhost:6006/vendors~main.c9781e3a7458a3b52f4d.bundle.js:141033:11) at HTMLUnknownElement.callCallback (http://localhost:6006/vendors~main.c9781e3a7458a3b52f4d.bundle.js:121452:14) at Object.invokeGuardedCallbackDev (http://localhost:6006/vendors~main.c9781e3a7458a3b52f4d.bundle.js:121501:16) at invokeGuardedCallback (http://localhost:6006/vendors~main.c9781e3a7458a3b52f4d.bundle.js:121556:31) at flushPassiveEffectsImpl (http://localhost:6006/vendors~main.c9781e3a7458a3b52f4d.bundle.js:144117:9) at unstable_runWithPriority (http://localhost:6006/vendors~main.c9781e3a7458a3b52f4d.bundle.js:170649:12)

Not sure how I can get rid of it?

My storybook file ReactTypical.stories.tsx is so simple:

I'm working with the TSDX tool to build a react-typescript library. I have a number of types exported in my @types/ directory which are clearly picked up by the compiler as I use them within the app with no trouble.

However, during my build, they do not get copied into my output bundle, which surprises me, since they are referenced through the code (which does get bundled correctly).