npm run build vs npm run watch when adding new commands

[sebastienlevert]

Hello team!

I'm working on my first ever command with the CLI for Microsoft 365 (!!!) and everything is actually going quite well! I have an issue with my dev workflow and I'm pretty sure you can help me out.

When I am creating a new command or even just changing a bit of the code, I would expect to be able to use npm run watch ad then open up a command prompt, running m365 and calling in my command, which is not the case. I need to run npm run build before I can test it out (I did my npm link earlier).

Is there any way to enhance this dev workflow or am I doing something completely wrong and I should just go hide? 🤣

Thanks!

[waldekmastykarz]

You're right and you should be able to use npm run watch. You need to run npm run build only once (after you cloned the repo or ran npm run clean which deletes the dist folder) because it includes a script that copies some file over after the project has been built.

What is the issue you're seeing with npm run watch exactly?

[sebastienlevert]

When using m365 * it always refer to the previously built CLI using npm run build, not the current.

[waldekmastykarz]

Could it be that you have installed CLI previously and your shell is using that version rather than the one from your dev folder? When you run npm ls -g --depth=0, can you see m365 pointing to your dev folder?

[sebastienlevert]

It was, but I just looked and had old references to o365 CLI and it seemed to have been the issue. Now everything's back to normal! Thanks for the help @waldekmastykarz!