You should be using the correct npm scope

[cobbdan]

You really need to fix your extension documentation as you are currently sending your customers to a random person's pet project.

Additionally, you should really be using the "@microsoft/poml" scope and package name.

https://www.npmjs.com/package/pomljs is not the same as https://www.npmjs.com/package/poml

yet your extension docs say to install that unvetted package: https://marketplace.visualstudio.com/items?itemName=poml-team.poml#node.js-via-npm-coming-soon

Situations like this is why npm has namespace scope: https://docs.npmjs.com/cli/v9/using-npm/scope

[ultmaster]

Yes. poml is taken. README has been fixed. I guess the vscode extension is still waiting for the next release for a fix.

There is no tradition to scope packages within microsoft. POML is not a Microsoft product, and scoping the package will make the length of import increase.