pnpm | Fast , disk space efficient package manager | Runtime Evironment library

Ok, the issue is that one of the modules in my app imported lodash cloneDeep like this

import cloneDeep from lodash/cloneDeep

i.e from the full lodash npm module.

Another of my modules imported it using the more targeted npm module using

import cloneDeep from "lodash.clonedeep"

A very confusing error message, but I suppose it makes some sense.

The fix was to import cloneDeep consistently, I chose the latter approach.

Yes, see https://pnpm.io/filtering

The problem is that when you call from PowerShell (unlike from cmd.exe), the command name dotenv resolves to a PowerShell script, namely dotenv.ps1, as you report.

When PowerShell calls a PowerShell-native command - including .ps1 files - its own parameter binder interprets the (first) -- argument and removes it; that is, the target command never sees it. (The semantics of -- is analogous to that of Unix utilities: -- tells the parameter binder to treat subsequent arguments as positional ones, even if they look like parameter (option) names, such as -foo.)

Thus, unfortunately, you need to specify -- twice in order to pass a single -- instance through to the .ps1 script itself:

This is extremely stupid mistake. I currently have 2 users in my machine setup and I was using the wrong one to deploy.

After performing aws configure with the credentials of the correct account I was able to deploy

1. The default behaviour in latest Commander is to display the help if you have subcommands and do not specify a subcommand. Which sounds like what you want! Not sure how you are getting an error, you might want to open a Commander issue for help.

2. In general, if you want some custom behaviour for no arguments then it may be simple and easy to check yourself before calling parse(). e.g.

Docs says that the build command npm install --prefix=../.. is only required if using npm workspaces, and doesn't apply when using pnpm or yarn workspaces. Since am using pnpm, I replace npm install --prefix=../.. with pnpm i -r and it worked.

In this case your best bet is an interactive rebase. But having merge commits makes that process a bit harder than usual.

You need to install those dependencies too if this warning shows up.

Copy all the packages listed below Peer dependencies that should be installed: and type this command:

You should add "automergeType": "branch". Ref: https://docs.renovatebot.com/noise-reduction/#branch-automerging