denoland / denoland/deploy_feedback

Github actions deployment failed due to local import not found.

Open
#264 1 comment 1 reaction 0 assignees View on GitHub
Dominant language
No language data
Stars
79
Forks
5
PR merge metrics
No merged PRs in 30d

Description

Source repository: https://github.com/metapages/metaframe-generic-js-runtime

Failed github action: https://github.com/metapages/metaframe-generic-js-runtime/runs/7815903455?check_suite_focus=true

Relevant file structure:

```
client/src/shared/config.ts
server/server.ts

```

Relevant error logs:

```
Entrypoint: file:///src/server/server.ts

...
Error: The deployment failed: Module not found "file:///src/client/src/shared/config.ts"
```

Running the server works locally:
```
deno run --allow-net server/server.ts
```

So perhaps the deployment logic doesn't like paths originating from a parent directory relative to the `Entrypoint`?

## Update

It fails even if I move the `config.ts` import right next to `server.ts`

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reading server/server.ts and client/src/shared/config.ts, then compare the failed GitHub Actions run with the local `deno run --allow-net server/server.ts` command. Reproduce the deployment failure and trace why the config import resolves to `file:///src/client/src/shared/config.ts`; done means the deployment completes successfully.

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
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.