codedoc update plugins doesn't work

This is a spin off of https://github.com/CONNECT-platform/coding-blog-plugin/issues/8#issuecomment-660163536

Quoting https://github.com/CONNECT-platform/coding-blog-plugin/issues/8#issuecomment-660030487

ok the CLI is updated (0.2.2) and from now on you should be able to update this plugin via:

codedoc update plugins

or

codedoc install @codedoc/coding-blog-plugin

codedoc update plugins doesn’t do anything for me but codedoc install @codedoc/coding-blog-plugin does. I can use the later command to update coding-blog-plugin from 0.1.10 to 0.1.11.

[loreanvictor]

ok so this seems like a weird behavior on part of NPM CLI. @bender2k14 could you open an issue on this repository (regarding behavior of npm update in .codedoc folder, since it definitely should update @codedoc/coding-blog-plugin to 0.1.11 in this case)? I could open an issue myself but I can’t replicate the behavior on my machine so perhaps there are some other configurations / parameters involved that I wouldn’t be able to provide to npm/cli maintainers should they need it.

[TysonMN]

Of course I didn’t mean to convey any form of urgency or priority for this, specifically as it is a non-breaking issue.

I enjoy helping others, so if I know it is on your mind, then I will make it happen.

Could you also paste the contents of .codedoc/package.json in the situation where there should be an update but codedoc/npm update doesn’t update anything?

Yep. Here is the link, but I copy-paste it here for convenience.

{
  "dependencies": {
    "@codedoc/coding-blog-plugin": "^0.1.10",
    "@codedoc/core": "^0.2.10"
  },
  "devDependencies": {
    "source-map-loader": "^1.0.0"
  }
}

I don’t mind continuing to test for you. If you wanted to try yourself though, you can checkout my repo at that commit.