denoland / denoland/deploy_feedback
Problem deploying to Deno Deploy when working with workspaces
- Dominant language
- No language data
- Stars
- 79
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Description
In a monorepo setup with multiple workspaces, deployment to Deno Deploy fails due to missing dependencies when setting a workspace as the project root.
Structure Example
```
/
├── libs/
│ └── mylibs.ts
└── web/
└── fresh_files/...
```
The web workspace imports from the libs workspace, like so:
```ts
import { someFn } from '@project/libs';
```
**Problem**
When deploying to Deno Deploy, you need to set /web/ as the project root. However, Deno Deploy does not include files outside the root directory (/web/) in the deployment bundle. As a result, any import from /libs/ fails with a runtime error due to missing files.
**Expected Behavior**
Deno Deploy should either:
Support importing files outside the root directory when using workspaces, or
Provide a mechanism to include these dependencies explicitly during build or deploy time.
**Environment**
Monorepo with multiple workspaces (/libs, /web)
**Deployment platform:** Deno Deploy
**Framework used:** fresh 2.0 alpha
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.