Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deno.json workspace support for Deno 2 #22942

Closed
11 of 12 tasks
Tracked by #23062
dsherret opened this issue Mar 15, 2024 · 4 comments
Closed
11 of 12 tasks
Tracked by #23062

deno.json workspace support for Deno 2 #22942

dsherret opened this issue Mar 15, 2024 · 4 comments
Assignees
Milestone

Comments

@dsherret
Copy link
Member

dsherret commented Mar 15, 2024

Tracking issue for unstable workspaces:

@dsherret dsherret added this to the 2.0 milestone Mar 15, 2024
@marvinhagemeister
Copy link
Contributor

Adding for completeness: I think the setup in Fresh is a bit odd given that the website is located inside the folder structure of Fresh itself.

<repo>/  # <- Fresh source here
  www/ # <- inside fresh/ folder

I would assume that we would switch to a each having their own directory when moving to workspaces:

<repo>/
  /fresh
  /www

The more important thing for me is if shared dependencies are properly hoisted to the top level workspaces folder to make deduplication work properly.

@bartlomieju bartlomieju changed the title Workspace support deno.json workspace support for Deno 2 Mar 31, 2024
@bartlomieju
Copy link
Member

When implementing this we should move as much code as possible to deno_config so other tools like dnt can reuse it.

@dsherret
Copy link
Member Author

Closing this as this will be released in Deno 1.45. Still pending documentation, but that will be completed later today.

@igl
Copy link

igl commented Jul 12, 2024

Amazing! Can't wait to try it out

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants