Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Curation of /x ?
See original GitHub issuehttps://deno.land/x has third party modules. Of the top 5 listed, only two actually work with /x. In order:
Does not work: https://deno.land/x/lodash does not mention Deno at all, and the maintainers are not interested in adding Deno examples
Does not work: https://deno.land/x/dayjs does not mention Deno at all, and the recommendation is to use skypack
Works: https://deno.land/x/sheetjs README is not loading but the README has Deno examples
Does not work: https://deno.land/x/xstate does not mention Deno in the main README.
There is a recipe that recommends skypack
Works: https://deno.land/x/corejs README has a Deno example.
If /x is intended as a host, it does not make sense to highlight modules that do not actually use or recommend /x.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@lucacasonato and I have talked about improving the “scoring” of packages based on a defined set of criteria. I realise there is no issue for that. I will open one, but to be clear,
deno.land/xdoesn’t curate nor “recommend” packages.The reason they don’t mention or even work in Deno is explained here: https://stackoverflow.com/a/69483910/16342352