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 Feb 26, 2024. It is now read-only.
we ship separate both cli and a core in one package, but cli should just use the bundled core as is.
The browser bundle is also a bit chunky, should this be shipped as a separate package? Or could we somehow make it use core (probably not, since it needs to polyfill many things)?
The text was updated successfully, but these errors were encountered:
uses ttsc NOT tsc, does transformations for you
npm run build, triggers webpack process
will try to build it even if its not compiled, always run tsc before running build
ts-loader doesnt pick up all the rules from tsconfig
if its not already compiled, then it will try to compile, but it will do it wrong
there are no tests for the build output, can write them if u want
webpack.common is where the bulk of the logic is
webpack.node is just core itself
webpack.cli is for cli
CORE
.node is native modules
ganache.min.js 3.2MB
35MB total
CLI
is almost exactly the same, pretty much the same code, but CLI is just a thin wrapper over core
but we are including an extra 30 MB when we publish
cli should just import the node one
we ship separate both cli and a core in one package, but cli should just use the bundled core as is.
The browser bundle is also a bit chunky, should this be shipped as a separate package? Or could we somehow make it use core (probably not, since it needs to polyfill many things)?
The text was updated successfully, but these errors were encountered: