Instead of using nvm (Node Version Manager), you can manage multiple Node.js versions using Homebrew and your

.zshrc

file. This approach involves installing different Node.js versions via Homebrew and updating your PATH environment variable to switch between versions.

Steps to Set Up

1. Install Node.js Versions via Homebrew:

    brew install node@16 node@18 node@20 node@22
   

2. Add the following line to your .zshrc file

# Node.js version (Change version number after "node@xx" to change your node version)
export PATH="/opt/homebrew/opt/node@20/bin:$PATH"

3. Switch Node.js Versions: To switch Node.js versions, change the version number in the export PATH line in your .zshrc file. For example, to switch to Node.js 18:

export PATH="/opt/homebrew/opt/node@18/bin:$PATH"

4. Apply Changes: Source your .zshrc file to apply the changes OR simply open a new terminal window.

source ~/.zshrc

Pros and Cons

Using Homebrew and .zshrc:

Pros:

• Simplicity: Straightforward setup and usage.

• Integration: Works seamlessly with Homebrew, which is commonly used on macOS.

• No Additional Tools: No need to install and manage an additional tool like nvm.

• Avoids the needs for nvm, which can have compatibility and installation issues on some machines.

Cons:

• Manual Updates: Requires manual editing of the .zshrc, instead of typing a terminal command.

• Limited Flexibility: Less flexible compared to nvm for quickly switching between versions or using different versions in different terminal sessions.

Using nvm:

Pros:

• Ease of Use: Simple commands to switch between Node.js versions (nvm use <version>).

• Flexibility: Allows different terminal sessions to use different Node.js versions.

• Project-Specific Versions: Supports .nvmrc files for project-specific Node.js versions.

Cons:

• There can be compatibility and installation issues on some machines.

• Additional Tool: Requires installing and managing nvm.

• Overhead: Slightly more overhead in terms of setup and learning curve.

Conclusion

Using Homebrew and .zshrc to manage Node.js versions is a simple and effective approach if you prefer minimal tooling and are comfortable with manual configuration. However, if you need more flexibility and ease of switching between versions, nvm might be a better choice.

Prerequisites:

1. An AWS Account, that you have configured on your machine using the AWS-CLI's aws configure command.

2. Install `AWS Copilot` by following their install steps here https://aws.github.io/copilot-cli/docs/getting-started/install/

3. Node.js version >=18 installed on your machine

Steps:

1. Create a new Next.js project based on the Docker Example by running npx create-next-app@latest --example=with-docker Link to example here: https://github.com/vercel/next.js/tree/canary/examples/with-docker

2. First cd into the Next.js app directory and run copilot init

3. Choose first option `App Runner`, and accept defaults for the rest of the prompts.

4. And HOSTNAME env variable to the service .yml file.

5. Visit the running Next.js application given in the terminal output.

6. Check Lighthouse Score

7. Run copilot app delete

1. Install git-filter-repo

2. clone both repos using --single-branch command.

https://github.com/redux-toolkit/tree/master

https://github.com/redux/tree/master

1. In the repo that contains the directory you want to move to the host repo, run
   git filter-repo --path FOLDER-NAME

2. Checkout a new branch on the host repo, in this case the `redux` repo.

   git checkout -b feat-move-packages-dir

3. In host repo, run git remote add -f local ../host-repo

4. In host repo run,
   git merge --allow-unrelated-histories local/master

References:

https://www.continuousimprover.com/2023/02/merging-repositories.html

https://docs.github.com/en/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository