Nathan Ridge

> hi @HighCommander4, i am happy to add you to npmjs/clangd org. can you provide your username? Thanks. Username is "nridge". > apart from that i tried cutting a new...

> > Could you clarify what the implications are of using this URL vs. https://registry.npmjs.org/ ? > > This URL points at the GitHub npm registry in the case that...

> Apologies, I copied the wrong line above.. > > > "registry": "https://npm.pkg.github.com" > > Is the GitHub one. Users would have to set up their `.npmrc` to have a...

> Thanks. I sent out #746 with this change. Merged. @kadircet this should now be ready for publishing (or giving me permissions to do so).

Thanks! Package published at https://www.npmjs.com/package/@clangd/vscode-clangd.

> As for yarn, I'm not quite sure how that works. I do see that `@clangd/install` shows up at https://yarnpkg.com/package?q=clangd&name=%40clangd%2Finstall; I suspect this may happen automatically (it's mirrored from npm)?...

Generally, a `compile_commands.json` file will contain an entry for every source file in a project, but not header files. For this reason, clangd's "command inference" feature is _usually_ needed only...

> So, if clangd find `compile_commands.json` file but can not retrieve the entry of exact match, it will do heuristics like this? Right, as that seems better than the alternative...

> Or at least, give a reminder that the file is interpreted using heristics. Thanks; I updated the title of the issue to reflect this suggestion.

The latter souds more appropriate to me, as it's not something the user needs to fix in the source.