-
Compilation fails while trying to compile the library with shadow-cljs.
The following error is shown.
```
The required namespace "decimal.extern.decimaljs" is not available, it was required by "dec…
-
## Problem
What do you think about completely removing the "Decimal" library from Prisma? It should be up to every development to decide if they want to use it. It is crashing all my Rest API defin…
-
Like PlainDate and more
https://tc39.es/proposal-temporal/docs/plaindate.html
-
### Verify Next.js canary release
- [X] I verified that the issue exists in the latest Next.js canary release
### Describe the bug
Non-default object types aren't picked up and you get the followin…
-
### Description
https://github.com/typestack/class-transformer/blob/develop/src/TransformOperationExecutor.ts#L160
TargetType is DecimalJS https://github.com/MikeMcl/decimal.js/blob/master/decimal…
-
### What do you want and why?
I noticed that if you use the type `Decimal` in your Prisma schema that the Prisma client uses `Decimal.js` instead of just a raw JS number. If you return a `Decimal` …
-
Kyle1297 is proposing to add decimal.js as a production dependency to Formula.js #123
If accepted, this should be generalized in the whole library (to avoid having a new dependency for 1 function)…
-
README says that `transform` should not throw errors. This makes it less convenient to use for two reasons:
1. If the code can throw errors, we need to ensure that they are caught and transformed to …
-
1. Convert decNumber to wasm and use that. (wasm-gc?)
2. If JS has a inbuilt method use it.
-
In a project using `type: module` the build fails as the top prima client import generated looks like this:
`import * as PrismaClient from "../../../node_modules/.prisma/client";`
The ESM proje…