ts-monorepo
io-ts
ts-monorepo | io-ts | |
---|---|---|
14 | 80 | |
1,427 | 6,602 | |
- | - | |
8.5 | 4.9 | |
6 days ago | 5 months ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ts-monorepo
-
[AskJS] Is there a silver bullet for consuming Typescript libraries in a Monorepo?
1. Linking libs with tsconfig paths. This approach involves setting a tsconfig.json paths object which maps the package name, to the local filesystem location. Eg. "paths": {"@org/lib":"../libs/lib"} - Nx uses this approach for their Integrated Monorepo configuration https://nx.dev/tutorials/integrated-repo-tutorial https://github.com/NiGhTTraX/ts-monorepo.
-
Recommendations for lerna/yarn mono repos?
FYI I tried renaming packages/bar/index.ts to index.js and adding allowJs: true in its tsconfig.json and tsconfig.build.json and everything works as expected.
-
Structuring packages and working with workspaces
Give https://github.com/NiGhTTraX/ts-monorepo a try :) It uses path aliases to map your imports to the source code inside the monorepo.
-
How to use npm workspace with create-react-app and typescript?
Make sure you've copied the jest craco config and that you've set up path aliases accordingly.
-
Handling TypeScript in a monorepo
You can check https://github.com/NiGhTTraX/ts-monorepo.
-
You might not need TypeScript project references
FWIW https://github.com/NiGhTTraX/ts-monorepo works in a similar way by using path aliases instead. The result is the same (imports resolve to monorepo source code), but this approach doesn't prevent you from publishing any of the packages (check the repo and the linked docs for more details).
-
using references in tsconfig.json to point to library code
You didn't give an example of how your imports look, but I'm assuming you're trying to use absolute imports for the lib files like from 'lib/src/...'. Project references don't rewrite the imports in any way, they just optimize the builds by caching referenced projects. You'll want to use path aliases instead. Feel free to check out https://github.com/NiGhTTraX/ts-monorepo for full examples.
-
[Question] Setting up monorepo: How be able to debug and build in the same project without changing package.json?
You can use two tsconfig.json files and in one of them configure path aliases to map your package names to the source code, effectively "overriding" package.json#main. You can find examples here https://github.com/NiGhTTraX/ts-monorepo.
-
Monorepo with Yarn Workspaces + TS + Docker Templates
Here is one I liked that is very basic, although I removed lerna from it personally. Shows examples of package sharing and a bunch of popular libraries. Next not nuxt but you get the idea. https://github.com/NiGhTTraX/ts-monorepo
- How do you manage TypeScript monorepos?
io-ts
-
TDD
Qué rico. Si tenés chance meté un proceso de code review fuerte, y para el tema de I/O probá a usar https://github.com/Effect-TS/schema ó https://github.com/gcanti/io-ts que les da una solución obvia al tema de "tipos para lo que devuelva el backend", aunque es en realidad mucho más capaz que eso.
-
Domain modelling with State Machines and TypeScript by Carlton Upperdine
My fave is still io-ts (https://github.com/gcanti/io-ts/blob/master/docs/index.md) as I find it more flexible than zod at the ingress. The author is also working on the Effect ecosystem which also looks interesting.
-
Why I Like Using Maps (and WeakMaps) for Handling DOM Nodes
I’ve been using io-ts for this and been very happy with it. [1] It’s similar to Swift’s Coding protocol in case you’re familiar.
[1] https://gcanti.github.io/io-ts/
-
Can someone recommend a library for data parsing similar to Zod, but with better support for input transformations/preprocessing?
Yeah, there are a few new concepts and it's not the easiest to pick up right away. The best introduction is here on the main documentation page.
- libraries you are happy that you discovered them
- Is React for small projects an Overkill?
-
how to strictly type this?
We use https://github.com/gcanti/io-ts/blob/master/Decoder.md which has a very similar interface. It can even be used to mutate the data using https://github.com/gcanti/io-ts/blob/master/Decoder.md#the-parse-combinator.
-
Typescript advanced bits: function overloading, never and unknown types
A good way to significantly improve the reliability of your app is via improving type-safety by moving away from using any to unknown. One relevant example could be when you type your backend responses and when stringifying JSON to using unknown combined with some sort of runtime type checking. It can be done either by using built-in functionality like type guards or using an external library like io-ts, zod or yup.
-
I found 10,000x faster TypeScript validator library
Usage of TypeBox is similar with io-ts and zod, but it is much powerful and faster than them. Also, TypeBox can generate JSON schema very easily. Therefore, if you're looking for a validator library for new project and not suffering from legacy codes, I think TypeBox would be much better choice than io-ts and zod. TypeBox can totally replace them.
-
Validate your data with Zod
This check can be done with different libraries like: io-ts, typebox, or zod. These libraries allow you to create objects that represent your typescript definitions. Then, these objects can be used at runtime to validate the received data, in addition, you can also convert this object to a Typescript definition to have all the benefits of using typescript. These objects can be called schema validations because they are responsible for the data validation.
What are some alternatives?
tsconfig-paths - Load node modules according to tsconfig paths, in run-time or via API.
zod - TypeScript-first schema validation with static type inference
babel-plugin-tsconfig-paths-module-resolver - Use tsconfig-paths in any bundler that supports a custom babel config.
class-validator - Decorator-based property validation for classes.
typescript-rollup - A Single-Page Application(SPA) built using TypeScript, Rollup.js, and Web Dev Server
openapi-generator - OpenAPI Generator allows generation of API client libraries (SDK generation), server stubs, documentation and configuration automatically given an OpenAPI Spec (v2, v3)
alias-hq - The end-to-end solution for configuring, refactoring, maintaining and using path aliases
runtypes - Runtime validation for static types
lerna-lite - Subset of Lerna in a smaller & more modular project. Helps manage and publish multiple packages in a monorepo/workspace structure
fp-ts - Functional programming in TypeScript
nestjs-monorepo-microservices-proxy - Example of how to implement a Nestjs monorepo with no shared folder
joi - The most powerful data validation library for JS [Moved to: https://github.com/hapijs/joi]