chore: remove lib dir from source-code & fix dev scripts #98
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Improvements
prepack
script which runs onnpm publish
and before packing up the package tarball. And theprepack
script just builds the package so that when npm publishes your package, It'll build the package first into alib
directory before publishing.schema.prisma
mongoDB should be removed from the previewFeatures array because in the latest Prisma release it's considered now as GA.package.json
from the package tarball, It's better to exclude it intsconfig.json
to skip compiling it which will also result in faster builds.removeComments: true
option intsconfig.json
to remove unnecessary comments from the build which will result in a smaller tarball size.start
script todev
cause usually start means a script to run an app in a production environment but in this case, It's for development(not a big deal though 😅)tsc -p .
cause it defaults to the current directory.sudo
from thelocal
script cause developers on windows won't be able to use this script if it was prefixed withsudo
(me included), If you have some issues on mac/linux when running this command withoutsudo
that's usually a permissions issue in your home directory which can be fixed by reclaiming the ownership of the.npm
directory