denoland / denoland/deploy_feedback
[Bug]: Fresh frontend failing to deploy due to 404 on deno std library module
- Dominant language
- No language data
- Stars
- 79
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
### Problem description
When I go to link my github repo for deployment, it fails with the following message:
```
Error The deployment failed: HTTP status client error (404 Not Found) for url (https://deno.land/std@0.188.0/encoding/_yaml/loader/loader.ts)
```
### Steps to reproduce
1. Write a simple front end.
2. Deploy to Deno Deploy
### Expected behavior
It should be able to find the encoder/_yaml module of the Deno std library.
### Environment
```
deno 1.33.3 (release, x86_64-apple-darwin)
v8 11.4.183.2
typescript 5.0.4
```
### Possible solution
_No response_
### Additional context
_No response_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the deployment with a simple frontend using the reported Deno 1.33.3 and TypeScript 5.0.4 environment, then inspect the failing request to the deno.land/std@0.188.0 encoding/_yaml/loader/loader.ts URL. Done means the frontend deploys successfully without the 404 module error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- deno, typescript
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100