Scoped packages not being passed to custom resolver
See original GitHub issueI was trying to work with the custom resolver to add all the polyfills/forks for packages, and realized it never resolved any of the namespaced packages.
I’ve been trying to see if I can get Tedious working in deno (since having mssql support in deno would be huge) and most of the dependencies work grabbing them from esm.sh, but the ones under @azure/
and @js-joda
never come through the custom resolver for me to be able to replace.
Issue Analytics
- State:
- Created a year ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
"scoped" packages · Issue #5239 · npm/npm - GitHub
@Raynos An argument to disallow publishing packages that depend on @org packages to the public registry is that, since the binding between @org ......
Read more >Cannot resolve scoped service from root provider .Net Core 2
What's happening there, is that the scope nesting isn't being validated; as in, it isn't checking, during runtime, if you have improper nesting ......
Read more >Resolvers - Apollo GraphQL Docs
A resolver is a function that's responsible for populating the data for a single field in your schema. It can populate that data...
Read more >scope - npm Docs
Scoped packages are not public by default. You will need to specify --access public with the initial npm publish command. This will publish...
Read more >Scoped registries - Unity - Manual
Scoped registries allow Unity to communicate the location of any custom ... custom packages in the Package Manager is the same as browsing...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It has been fixed in the last version of Keycloakify, thank you for reporting.
I can reproduce. I’ll address it.