Some more possible destinations

Neat tool! I can see how it will save time if I remember to use it!

Some of these are kinda random, some of these I actually use, but thought I’d just go for it, in case any of them strike a chord.

https://npmtrends.com/njt

npm-audit: https://www.gyanblog.com/tutorials/how-node-npm-audit-rest-api-vulnerability/

https://npmgraph.js.org/?q=njt

https://snyk.io/advisor/npm-package/njt

https://socket.dev/npm/package/njt

https://techgaun.github.io/active-forks/index.html#https://github.com/kachkaev/njt

[kachkaev]

I suggest that we figure out search autocompletion first as it will help with navigating between more destinations. We can frame the feature like this:

As a user, I should be able to type njt[space]prettier[space] and see a list of destinations.

I don’t have any experience with this kind of stuff bu I believe that we need a new API endpoint which can be auto-discovered by Chrome, FF, Alfred etc. When this is sorted, we can add autocompletion support to njt.vercel.app and CLI. This will unblock pretty much any number of destinations we want. Adding two-letter destinations now will make the tool harder to use because it’s difficult to remember a lot of abbreviations.

[kachkaev]

👋 @mrienstra! njt CLI is just one of several user interfaces (entry points) for njt. If we add more keywords and figure out UX for cli, other environments like browsers, Alfred, etc. may degrade UX-wise. More keywords means more cognitive load on a human and therefore higher chances of landing on the wrong page.

Before we add more keywords, what we probably need is a universal way of providing search prompts for the query (like Google does when we type text in the browser’s address bar). Maybe we should explore this direction first, find a universal solution and then port it to all interfaces we have (which will include CLI). WDYT?