(no title)
arcatek | 3 years ago
This way, we can use babel-node or ts-node to transparently run our TS files, no transpilation needed.
arcatek | 3 years ago
This way, we can use babel-node or ts-node to transparently run our TS files, no transpilation needed.
cas8|3 years ago
Wouldn’t that mean the shared packages tsconfigs aren’t respected if you changed something like strict options? And also that a clean build of the whole monorepo is going to recompile each shared file for every app project rather than just once?
sevenf0ur|3 years ago
bsimpson|3 years ago
Moving forward, I'm going to use wireit for these things. Pure modules get built with tsc. At the highest level (e.g. where it needs to be embedded in a page), make a bundle with rollup.
wireit has two nice properties: incremental building and file-system-level dependencies. Within a repo, you can depend on ../package-b. However, if you have multiple monorepos that often get used together, you can also depend on ../../other-project/packages/package-b. No matter where in your tree you make changes, wireit knows when to make a new bundle.
I've just started with wireit (it was only launched recently), but it seems to be a nice solution to wrangling dependencies between related JS libraries.
[1] https://github.com/google/wireit
forty|3 years ago
https://github.com/pnpm/pnpm/blob/main/.meta-updater/src/ind...