deno-postgres@v0.4.4 seems not to be published in deno's module registry
See original GitHub issueDescription
Importing deno-postgres@v0.4.4 returns 404 error:
Download https://deno.land/x/postgres@v0.4.4/mod.ts
error: Import 'https://deno.land/x/postgres@v0.4.4/mod.ts' failed: 404 Not Found
Possible cause & solution
I think this problem is due to the recent changes in the registry. This problem can be solved by setting up a webhook in this repository.
Ref
Issue Analytics
- State:
- Created 3 years ago
- Reactions:9
- Comments:7 (2 by maintainers)
Top Results From Across the Web
terraform registry stuck publishing module #30691 - GitHub
While trying to publish my module, It got stuck in publishing state, And when I am trying to republish it then it is...
Read more >How to publish Deno modules - DEV Community
Deno Land Registry · Navigate to the repository you want to add. · Go to the Settings tab. · Click on the Webhooks...
Read more >Publishing Modules - Terraform Registry - HashiCorp Developer
Anyone can publish and share modules on the Terraform Registry. ... do not see the version appear, since it will cause the registry...
Read more >Building Your Module Empire - YouTube
Do you use a mix of private modules and modules from registry.terraform.io? This talk will show you how to use the Registry Modules...
Read more >Import Suggestions and Intelligent Registries | Manual - Deno
The language server, supports completions for URLs. Local import completions. When attempting to import a relative module specifier (one that starts with ./...
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 Free
Top 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

@hayd deno is now onto v1.4.0 - may we have an update, when available?
Thanks for resolving this @hayd!