Added NPM to Glossary and linked to mentions - #7283

Thanks for the patch @nihalshetty-boop, it's queued for review.

Glad I could help :-)

Rendered docs seem to behave as expected: https://numba--7283.org.readthedocs.build/en/7283/developer/numba-runtime.html?highlight=npm

but please could the lines be wrapped to 80 chars?

@stuartarchibald I'm sorry I didn't quite understand, can you elaborate on this? Should I decrease the character count of the PR Description to 80 characters?

but please could the lines be wrapped to 80 chars?

@stuartarchibald I'm sorry I didn't quite understand, can you elaborate on this? Should I decrease the character count of the PR Description to 80 characters?

Understood the issue and fixed in commit Wrapped Line Characters to <= 80.

(Right now the latest round of failed tests is shown in the bottom because you have not pushed any new commits yet. In general you can inspect previous test runs by clicking on the small red cross ❌ or green check mark ✔️ next to the fingerprint of the commit)

@HPLegion Great, thank you for helping me out, I've corrected the indentation now :)

@HPLegion Awesome! If an issue could be raised about

There are a couple of cosmetic changes that could be made to this file (line length violations, double spaces)

I would be interested in working on it. I'm not sure if I can raise issues as a first time contributor.

I would be interested in working on it. I'm not sure if I can raise issues as a first time contributor.

Anyone can - and should - open issues if they see any :-)
For a maintenance issue like this, where you already know what the problem is, an issue is probably not even needed. You can just fix it and make a PR explaining what you did and why (in my opinion).

That said, I'd wait for feedback from a core maintainer here, to see how they feel about this. Maybe they actually prefer if those changes are integrated here.

Secondly, if you start working on this now, before this PR is merged into master, then you will likely run into merge conflicts with your cosmetics branch later, because some of the changes will touch on the same lines as this PR. If you see that as an annoyance or as a possibility to learn dealing with conflicts, is up to you to decide ;-)

Yes, it's better to wait till this PR has been merged 👍

@HPLegion many thanks for providing guidance throughout this PR and for reviewing it, it's much appreciated.

@nihalshetty-boop, @HPLegion , I'd say it's fine to just open PRs for cosmetic fixes to e.g. docs that are quick to do and unlikely to be controversial. It's entirely fine to open PRs for anything, but obviously if there's a lot of work involved it's generally a good idea to open an issue about it first so as to gather feedback prior to starting the work to ensure that the PR has a good chance of being merged etc.

RE additional changes. To save merge conflict issues I'd either wait for this PR to be merged (probably in the merge window later today) or to base a new PR off this branch and then when this patch is merged git/github will just figure out the diff.

@nihalshetty-boop Congratulations on your first contribution to Numba!

Thank you!