node/ npm / nodejs

1. others

1.1. styles

1.1.1. bad

1.1.1.1. Very bad

1.1.2. good

1.1.2.1. very good

1.1.3. not as good

1.1.4. not as bad

1.1.5. important

1.1.5.1. Very important

1.1.6. warning

1.1.7. link

1.2. AUTHOR

1.2.1. Nima Shokouhfar

1.2.1.1. Linkedin

1.2.1.1.1. Follow me on LinkedIn to stay updated on my latest professional insights and tech projects!

1.2.1.2. Youtube

1.2.1.2.1. code with nima

1.2.1.2.2. ideariver

1.2.1.3. Medium

1.2.1.3.1. ✍️ Follow me on Medium to read my latest articles on tech, coding, and innovation!

1.2.1.4. Github

1.2.1.4.1. ⭐️ Give my projects a star on GitHub and explore my repositories to discover new tools and innovations!

1.2.1.4.2. 💖 Sponsor me on GitHub to support my open-source contributions and help me create even more useful projects!

1.2.1.5. upwork

1.2.1.5.1. 💼 Hire me on Upwork for freelance projects. Let’s work together to bring your tech ideas to life!

1.2.1.6. main website: ideariver.ca

1.2.1.6.1. 🚀 Visit IdeaRiver.ca for all my latest projects, blogs, and ways to connect!

2. main

2.1. set to default registery

2.1.1. npm config set registry https://registry.npmjs.org/

2.1.2. npm config set registry https://registry.npmjs.org/

2.2. .npmrc

2.2.1. Global .npmrc: This is typically located in your home directory.

2.2.1.1. On Linux/Mac: ~/.npmrc

2.2.1.2. On Windows: C:\Users\<YourUsername>\.npmrc

2.2.2. format of the file for private repos

2.2.2.1. //<custom_registry_url>/:_authToken=<auth_token>

2.2.2.2. the default is

2.2.2.2.1. registry=https://registry.npmjs.org/

2.2.3. to fix react bug:

2.2.3.1. legacy-peer-deps=true

2.2.4. scoped

2.2.5. npm install --userconfig ./.npmrc

2.3. link

2.3.1. vid

2.3.2. good one

2.3.2.1. 2

2.3.3. to access dependencies locally

2.3.4. doc

2.3.4.1. npm link --workspace <name>

2.3.5. commands

2.3.5.1. npm link

2.3.5.2. npm link package-name

2.3.5.3. npm unlink package-name

2.3.5.4. npm -ls link

2.3.6. Bug

2.3.6.1. I am not sure, But i think it messed up my tsconfig.json

2.3.6.1.1. more photo

2.4. scoped

2.4.1. Scoped npm packages are a way to group related packages together under a common namespace.

2.4.1.1. importing the package

2.4.1.2. 2

2.5. Commands

2.5.1. remove installed packages

2.5.1.1. rm -rf node_modules package-lock.json yarn.lock

2.5.1.2. upgrade to the latest

2.5.1.2.1. npm install ideariver.core@latest

2.5.2. npm install ideariver.core@latest

2.5.2.1. upgrade the package to the latest one

2.6. publish to npm

2.6.1. very good video

2.6.1.1. lint to make sure nothing is broken

2.6.1.2. changeset

2.6.1.2.1. help on package versioning documentation

2.7. react issue

2.7.1. --legacy-peer-deps=true

2.8. switching node version for legacy projects developments

2.8.1. issue

2.8.1.1. The error you're encountering is related to TypeScript's moduleResolution option not being properly set for the project. The root cause is likely a mismatch between the required Node.js version, TypeScript configuration, and dependencies in the project.

2.8.1.2. Since you're using Node.js v20.14.0, there might be compatibility issues with this newer version. Many popular repositories are still tested primarily on Node.js v16 or v18.

2.8.2. solution

2.8.2.1. switching between node versions using node manager

2.8.3. Tut

2.8.3.1. link to setup.exe

2.9. NVM

2.9.1. commands

2.9.1.1. nvm install 16

2.9.1.1.1. nvm install 20

2.9.1.2. nvm use 16

2.9.1.3. node -v

2.9.2. My original version was

2.9.2.1. v20.14.0

2.10. version

2.10.1. Semantic versioning follows the format:

2.10.1.1. MAJOR.MINOR.PATCH

2.10.1.1.1. - **MAJOR**:

2.10.1.1.2. - **MINOR**:

2.10.1.1.3. - **PATCH**:

2.10.2. example

2.10.2.1. "version": "1.0.10"

2.10.2.1.1. ### Breakdown of "1.0.10":

2.10.2.1.2. ### Conclusion: