ts-monorepo VS lodash

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

Lodash.js is like the Swiss Army knife for JavaScript developers. Need to manipulate data structures or dabble in functional programming? Lodash is here to save the day with its arsenal of utilities. It's all about making your code cleaner and your life easier, which is probably why big guns like Google and Airbnb have it in their toolkit.

lodash - utility library enabling things like deep object comparison that aren't easy to do with javascript out of the box. docs

Lodash is a widely used JavaScript utility library that provides a plethora of functions to simplify common programming tasks. From manipulating arrays and objects to handling edge cases and implementing functional programming paradigms, Lodash offers a comprehensive toolkit for JavaScript developers. In this beginner's guide, we'll learn how to get started with Lodash and leverage its functionality to write cleaner, more efficient, and more maintainable code.

5. Lodash

If you want even more sophisticated equality checks like deep comparisons, there's the: lodash.iseQual library that'll do this for you out of the box. At least now you do have a bit of clarity on what's happening under the hood, so there's no harm in using a library.

It's also important to ensure that you're importing libraries correctly, so webpack can perform tree shaking effectively. For example, let's import lodash, as follows:

Lodash is awesome! It’s a JavaScript library that helps you do many things with data. You can use Lodash to manipulate arrays, objects, JavaScript strings, numbers, and more. It’s easy to get Lodash in your project. You can use npm or a CDN to install and import it. Here’s how:

Think of RxJS as Lodash for events.

lodash and You Might Not Need Lodash

A lot of Lodash functions are implemented as combinations of other Lodash functions, so importing a single function actually imports half of Lodash under the hood:

https://github.com/lodash/lodash/blob/main/src/.internal/bas...