Workspaces #64
Workspaces #64
Conversation
There was a problem hiding this comment.
The workspaces setting seems blocked by vercel-community/deno
Everything in .vscode/.github looks good to me so if you'd like to merge these changes now you could open a separate PR
As for the lint.tags I'd prefer keeping it less verbose since it's already the default
| "run/", | ||
| "testing/", | ||
| "typing/", | ||
| "xml/" |
There was a problem hiding this comment.
It makes vercel deployments fail with the following:
error: Workspace member 'bundle/' has no deno.json file ('/vercel/path1/bundle/deno.json')
Error: Build script failed with exit code 1
I think it's related to denoland/deno#23343 and the fact that the vercel-community/deno uses 1.42.1 currently.
I know you can pass a --version flag to them according to their docs, but I'll prefer it to not do as it does not make sense to break lambdas just because of a conf change which is enterily not related to actual code.
I'll wait for a version bump on their side before merging this
There was a problem hiding this comment.
Deno workspaces enable JSR dependencies to resolve to local copies. This essentially turns all of the packages' tests into tests for `@libs/testing`.
Deno is rolling out a new feature called workspaces.
It enables JSR monorepos to link to packages locally.
While
libsis far less interconnected thandeno_std, I figured that it might help if@libs/testinggot some extra "tests" by having all the packages link to the local copy in development.It should also enable a single dependency resolve and (probably) obsolete deno_config.ts, as I believe it automatically syncs formatting/linting/etc.