pnpm VS eslint-plugin-import

Pnpm for install Javascript/Typescript packages, like LangChain.js

Node.js manages dependencies using package managers like npm (Node Package Manager), yarn, and pnpm. npm comes pre-installed with Node.js and allows you to install and uninstall Node.js packages. It uses a package.json file to keep track of which packages your project depends on. Yarn and Pnpm are alternative package managers that aim to improve on npm in various ways, such as improved performance and better lock file format.

Use pnpm - This is just one recommendation, but it's too big of a topic to discuss here.

In this blog post, I explain how to use pnpm in GitLab CI and how to authenticate with a private GitLab package registry.

A package manager such as npm, Yarn, or pnpm. A package manager is a tool that helps you manage the dependencies of your project. You can use any of these package managers to install Jest and other packages.

Installation: Install Redux and React-Redux using npm or yarn.(you can try pnpm too!)

I also recommend using pnpm as a package manager, it's faster and more efficient than npm or yarn with great capabilities concerning monorepo setup. On recent nodejs versions (v16.13+), you can install it easily with:

[2]: https://github.com/import-js/eslint-plugin-import/pull/2447#...

Finally, I'd also suggest requiring named exports via import:

eslint-plugin-import

You can 1. use a rule like this one to ensure that no one imports from antd and 2. limit what they can import from your library via https://nodejs.org/api/packages.html#main-entry-point-export

I'd check the eslint docs. They usually have a little write up about the rule.

Next, you add the ESLint rule or TypeScript configuration so it never happens again.

Are you using Eslint? It is possible to remove all the unused import on file level, but I don't remember if the setting is in the recommend config or the import/ordef plugin. If configured correctly, VS Code will prompt you with an option (CTRL+.) to "Delete all unused imports". It's only on file level though.

Prefer default export (from airbnb style guide) I did drop default exports for a year now to use only named exports and they are actually (a slightly) better option. They provide a better DX, since you'll have autocomplete. The downside can be conflicts (which can be solved using an as to rename it). Don't refactor your entire codebase just to use it, but keep in mind for the next projects that named exports has better tradeoffs.

Yeah, the code under server should never get included unless you were to (transitively) import it from your entry point like App.tsx. Small suggestion, this is a good candidate for an ESLint rule if you use that.