vscode-runme
vscode-runme copied to clipboard
stateful
DevOps Workflows Built with Markdown for VS Code
Bumps [qs](https://github.com/ljharb/qs) from 6.5.2 to 6.5.3. Changelog Sourced from qs's changelog. 6.5.3 [Fix] parse: ignore __proto__ keys (#428) [Fix] utils.merge: avoid a crash with a null target and a truthy...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
Bumps [express](https://github.com/expressjs/express) from 4.17.1 to 4.18.2. Release notes Sourced from express's releases. 4.18.2 Fix regression routing a large stack in a single route deps: [email protected] deps: [email protected] perf: remove unnecessary...
- [x] Fast-forwarded baseline to latest `main` - [x] Implemented first integration of Serializer WASM interface - [ ] Complete `metadata` exchange in Serializer to make downstream functionality work -...
Implements #70 This patch implements a task provider for Runme related executions. It allows us to merge our previous `shell` and `task` executor into one and allow to stream stdout...
Consider finding new home for a `deno deployctl` example. https://github.com/stateful/runme.dev had to transition platform and deploy to unlock Docusaurus. Let's have a Fresh showcase app.
VSCode metadata: Version: 1.73.1 (Universal) Commit: 6261075646f055b99068d3688932416f2346dd3b Date: 2022-11-09T02:08:38.961Z Electron: 19.0.17 Chromium: 102.0.5005.167 Node.js: 16.14.2 V8: 10.2.154.15-electron.0 OS: Darwin x64 20.6.0 Sandboxed: No Screenshot of errors: 
Proof reliable access to stdio and support for non-trivial TUX (character device and VT sequence stuff).
Do we still have to include `node_modules` in packaging? I believe in the past we kept the `node_modules` because of the web component stuff, no?
- contributing - code of conduct - development.md - clean up readme
