Concis VS ts-monorepo

[concis github](https://github.com/fengxinhhh/Concis)

cimi github concis github concis documentation

I hope that the small partners in the community who are interested can leave me a message through the [issue](https://github.com/fengxinhhh/Concis/issues) of [github](https://github.com/fengxinhhh/Concis). I Will take the initiative and actively contact. If you think this repository is not bad, you can give me a star or tell your friends, I need it to be seen by more people. Work devoutly and be grateful. Thank you.

# What is Concis?

A brief introduction for those who are not familiar with this project. Concis is a lightweight component library developed based on React+TypeScript. It fully embraces the React ecosystem and supports new React features (hooks/redux) to pursue lightweight components. Component volume, simple use, minimal thinking burden.


[Github](https://github.com/fengxinhhh/Concis)

[Official Documentation](http://react-view-ui.com:92/)

# Why are you looking for teammates?

From the commit record of github, we can know that from Concis init commit to now, only bloggers are doing iterative development by themselves, and they use time outside of work to maintain and develop this repository. In fact, there are still many places to improve Concis as follows. Bloggers hope to find friends who like toss and study in the community to develop together to create an ecology and community.

# next plan

At present, the component library blogger has sorted out some points that can be started, as follows:

- The number of components is relatively small, and it is expected to expand to 50~60;

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.

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.

Give https://github.com/NiGhTTraX/ts-monorepo a try :) It uses path aliases to map your imports to the source code inside the monorepo.

Make sure you've copied the jest craco config and that you've set up path aliases accordingly.

You can check https://github.com/NiGhTTraX/ts-monorepo.

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).

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.

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.

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