wilsonlewis
Workspace member parallel processes (monorepo)
In the Node based monorepo tools I have used, when you run a "task" at the root of the workspace, it will run that same "task" in each workspace in parallel
For example, I can run "deno task dev" at the root of the repository and it will run "dev" in each workspace member as a way to spin up each of the services I am working on in one command
Is this something that is built into Deno Workspace?
4 replies
Deno + Vite + React + VSCode
Could someone help me setup VSCode so that it recognizes React JSX without red squiggles?
Also, is it possible to setup type reference for image imports from vite?
I have been at this for a couple days and still can't figure it out...
3 replies
EventSource vs Multiplex webook
I am setting up an system that needs realtime updates for potentially 100+ different resources on a page.
Unfortunately, I'm not familiar with how Deno Deploy handles EventSource connections
So, based on Deploy infrastructure, would it be advisable to use 1-1 EventSource for each resource?
Or, should I have a single Websocket connection that multiplexes all the resources?
Thanks!
2 replies
Manual deployment promotion + long lived preview deployments
Hello! I am working on a deployment pipeline and have a few questions:
1. Is there a way to promote preview deployments to production from a github actions?
- I would like to deploy a preview deployment, run my own smoke tests and then promote to production
2. How long do preview deployments last?
- Is there a scenario where one project needs to reference an older version of a different project?
- This is in an effort to combat api drift. I would like one projects to target a specific version of a different project
Thanks!
3 replies