You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 14, 2021. It is now read-only.
A lot of project in Javascript/Typescript ecosystem use a module/asset bundler for various reasons like tree-shaking, transpiling, code-splitting, and more.
While all the bundlers have APIs to copy the assets, it is not transparent that binaries act as assets for Prisma Client.
Some bundlers (like ncc, parse path.join and copy over required assets while others don't). This leads to confusion.
This issue tracks improvement of the developer experience around this.
The text was updated successfully, but these errors were encountered:
janpio
changed the title
Photon and Javascript bundlers
Prisma Client and Javascript bundlers
Sep 12, 2020
A lot of project in Javascript/Typescript ecosystem use a module/asset bundler for various reasons like tree-shaking, transpiling, code-splitting, and more.
While all the bundlers have APIs to copy the assets, it is not transparent that binaries act as assets for Prisma Client.
Some bundlers (like
ncc
, parsepath.join
and copy over required assets while others don't). This leads to confusion.This issue tracks improvement of the developer experience around this.
The text was updated successfully, but these errors were encountered: