Unable to debug cli-microsoft365 locally

[sprider]

Hi Team,

I have started developing a new command(#2164) and trying to debug my code locally using npm link but my local cli is not recognizing the new command. Any tips to troubleshoot this issue?

Thank you in advance !

• mkdocs.yml
• policy-list.md
• commands.ts
• policy-list.ts
• policy-list.spec.ts - not started the development for this.

[waldekmastykarz]

When you type npm ls -g --depth=0, can you see CLI registered and pointing to your local folder?
What version of npm are you using? Have you tried unlinking and re-linking CLI?

[sprider]

@waldekmastykarz, Thank you for your time to review my issue ! Please find the detials below :

• I can see CLI registered and pointing to my local folder.
• npm version : 7.6.0
• Tried unlinking but @pnp/cli-microsoft365 is not getting removed

[waldekmastykarz]

Are you unlinking it using npm -g un? Starting from npm@7 you have to explicitly use -g. If that also doesn't help, you could try manually removing the symlink by navigating to the folder where they're stored (the path is listed as one of the first lines of npm ls -g --depth=0 output) and deleting the @pnp/cli-microsoft365 folder.

[sprider]

@waldekmastykarz, Thank you so much for your reply. -g did the trick. I am able to link my local cli and debug.

[waldekmastykarz]

Great to hear you're unblocked. npm@7 changed this behavior and -g tripped me up as well.