2023-04-25 11:01:25 +00:00
|
|
|
{
|
|
|
|
|
"name": "@tldraw/scripts",
|
|
|
|
|
"description": "build scripts",
|
|
|
|
|
"version": "2.0.0-alpha.8",
|
|
|
|
|
"private": true,
|
|
|
|
|
"author": {
|
2023-12-19 10:41:01 +00:00
|
|
|
"name": "tldraw Inc.",
|
2023-04-25 11:01:25 +00:00
|
|
|
"email": "hello@tldraw.com"
|
|
|
|
|
},
|
|
|
|
|
"homepage": "https://tldraw.dev",
|
2023-12-19 10:41:01 +00:00
|
|
|
"license": "SEE LICENSE IN LICENSE.md",
|
2023-04-25 11:01:25 +00:00
|
|
|
"repository": {
|
|
|
|
|
"type": "git",
|
|
|
|
|
"url": "https://github.com/tldraw/tldraw"
|
|
|
|
|
},
|
|
|
|
|
"bugs": {
|
|
|
|
|
"url": "https://github.com/tldraw/tldraw/issues"
|
|
|
|
|
},
|
|
|
|
|
"keywords": [
|
|
|
|
|
"tldraw",
|
|
|
|
|
"drawing",
|
|
|
|
|
"app",
|
|
|
|
|
"development",
|
|
|
|
|
"whiteboard",
|
|
|
|
|
"canvas",
|
|
|
|
|
"infinite"
|
|
|
|
|
],
|
|
|
|
|
"devDependencies": {
|
2024-01-16 14:38:05 +00:00
|
|
|
"@actions/github": "^6.0.0",
|
2024-02-26 10:06:23 +00:00
|
|
|
"@auto-it/core": "^11.1.1",
|
2024-01-16 14:38:05 +00:00
|
|
|
"@aws-sdk/client-s3": "^3.440.0",
|
|
|
|
|
"@aws-sdk/lib-storage": "^3.440.0",
|
2023-04-25 11:01:25 +00:00
|
|
|
"@types/is-ci": "^3.0.0",
|
2024-01-31 16:53:40 +00:00
|
|
|
"@types/node": "~20.11",
|
[docs] Sync docs deploy with npm deploy (#3153)
This PR makes it so that our docs deployment process is tied to, and
mirrors, the npm deployment process.
From here on:
- Commits to main get deployed to staging.tldraw.dev
- Commits to a special protected branch called `docs-production` get
deployed to www.tldraw.dev
- Whenever we create a new npm 'latest' release we reset the HEAD of
docs-production to point to the tagged commit for that release.
- If we make a docs change that we want to appear on tldraw.dev ASAP
without waiting for the next npm release, we'll have to follow the same
process as for creating a patch release i.e merge a cherry-pick PR
targeting the latest release branch e.g. `v2.0.x`. This will not cause
another npm patch release unless the cherry-picked changes touch source
files, e.g. updating TSDoc comments.
### Change Type
- [x] `docs` — Changes to the documentation, examples, or templates.
- [x] `tools` — Changes to infrastructure, CI, internal scripts,
debugging tools, etc.
2024-03-14 14:43:32 +00:00
|
|
|
"@types/tar": "^6.1.11",
|
2023-04-25 11:01:25 +00:00
|
|
|
"@typescript-eslint/utils": "^5.59.0",
|
|
|
|
|
"ast-types": "^0.14.2",
|
|
|
|
|
"cross-fetch": "^3.1.5",
|
2023-07-18 10:19:28 +00:00
|
|
|
"esbuild": "^0.18.4",
|
2024-01-30 11:41:46 +00:00
|
|
|
"eslint": "^8.37.0",
|
2023-04-25 11:01:25 +00:00
|
|
|
"glob": "^8.0.3",
|
2023-06-23 14:23:14 +00:00
|
|
|
"gray-matter": "^4.0.3",
|
2023-04-25 11:01:25 +00:00
|
|
|
"is-ci": "^3.0.1",
|
|
|
|
|
"kleur": "^4.1.5",
|
2023-06-05 17:32:32 +00:00
|
|
|
"lazyrepo": "0.0.0-alpha.27",
|
2024-01-15 12:33:15 +00:00
|
|
|
"prettier": "^3.0.3",
|
2023-04-25 11:01:25 +00:00
|
|
|
"recast": "^0.22.0",
|
|
|
|
|
"rimraf": "^4.4.0",
|
|
|
|
|
"semver": "^7.3.8",
|
|
|
|
|
"svgo": "^3.0.2",
|
2024-02-25 11:43:17 +00:00
|
|
|
"typescript": "^5.3.3"
|
2023-04-25 11:01:25 +00:00
|
|
|
},
|
|
|
|
|
"scripts": {
|
|
|
|
|
"lint": "yarn run -T tsx lint.ts"
|
2023-06-02 10:45:51 +00:00
|
|
|
},
|
|
|
|
|
"dependencies": {
|
2024-03-12 14:53:57 +00:00
|
|
|
"@octokit/rest": "^20.0.2",
|
2024-02-29 12:21:11 +00:00
|
|
|
"@types/minimist": "^1.2.5",
|
[docs] Sync docs deploy with npm deploy (#3153)
This PR makes it so that our docs deployment process is tied to, and
mirrors, the npm deployment process.
From here on:
- Commits to main get deployed to staging.tldraw.dev
- Commits to a special protected branch called `docs-production` get
deployed to www.tldraw.dev
- Whenever we create a new npm 'latest' release we reset the HEAD of
docs-production to point to the tagged commit for that release.
- If we make a docs change that we want to appear on tldraw.dev ASAP
without waiting for the next npm release, we'll have to follow the same
process as for creating a patch release i.e merge a cherry-pick PR
targeting the latest release branch e.g. `v2.0.x`. This will not cause
another npm patch release unless the cherry-picked changes touch source
files, e.g. updating TSDoc comments.
### Change Type
- [x] `docs` — Changes to the documentation, examples, or templates.
- [x] `tools` — Changes to infrastructure, CI, internal scripts,
debugging tools, etc.
2024-03-14 14:43:32 +00:00
|
|
|
"@types/tmp": "^0.2.6",
|
2024-01-16 14:38:05 +00:00
|
|
|
"ignore": "^5.2.4",
|
2024-02-29 12:21:11 +00:00
|
|
|
"minimist": "^1.2.8",
|
Bump the npm_and_yarn group across 1 directory with 2 updates (#3505)
Bumps the npm_and_yarn group with 2 updates in the / directory:
[vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) and
[tar](https://github.com/isaacs/node-tar).
Updates `vite` from 5.2.8 to 5.2.9
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md">vite's
changelog</a>.</em></p>
<blockquote>
<h2><!-- raw HTML omitted -->5.2.9 (2024-04-15)<!-- raw HTML omitted
--></h2>
<ul>
<li>fix: <code>fsp.rm</code> removing files does not take effect (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/16032">#16032</a>)
(<a href="https://github.com/vitejs/vite/commit/b05c405">b05c405</a>),
closes <a
href="https://redirect.github.com/vitejs/vite/issues/16032">#16032</a></li>
<li>fix: fix accumulated stacks in error overlay (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/16393">#16393</a>)
(<a href="https://github.com/vitejs/vite/commit/102c2fd">102c2fd</a>),
closes <a
href="https://redirect.github.com/vitejs/vite/issues/16393">#16393</a></li>
<li>fix(deps): update all non-major dependencies (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/16376">#16376</a>)
(<a href="https://github.com/vitejs/vite/commit/58a2938">58a2938</a>),
closes <a
href="https://redirect.github.com/vitejs/vite/issues/16376">#16376</a></li>
<li>chore: update region comment (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/16380">#16380</a>)
(<a href="https://github.com/vitejs/vite/commit/77562c3">77562c3</a>),
closes <a
href="https://redirect.github.com/vitejs/vite/issues/16380">#16380</a></li>
<li>perf: reduce size of injected __vite__mapDeps code (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/16184">#16184</a>)
(<a href="https://github.com/vitejs/vite/commit/c0ec6be">c0ec6be</a>),
closes <a
href="https://redirect.github.com/vitejs/vite/issues/16184">#16184</a></li>
<li>perf(css): only replace empty chunk if imported (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/16349">#16349</a>)
(<a href="https://github.com/vitejs/vite/commit/e2658ad">e2658ad</a>),
closes <a
href="https://redirect.github.com/vitejs/vite/issues/16349">#16349</a></li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/vitejs/vite/commit/a77707d69ca53d21e6c7ae9256683ecd3f1d721e"><code>a77707d</code></a>
release: v5.2.9</li>
<li><a
href="https://github.com/vitejs/vite/commit/102c2fd5ad32a607f2b14dd728e8a802b7ddce34"><code>102c2fd</code></a>
fix: fix accumulated stacks in error overlay (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/16393">#16393</a>)</li>
<li><a
href="https://github.com/vitejs/vite/commit/58a2938a9766981fdc2ed89bec8ff1c96cae0716"><code>58a2938</code></a>
fix(deps): update all non-major dependencies (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/16376">#16376</a>)</li>
<li><a
href="https://github.com/vitejs/vite/commit/77562c3ff2005c7ca7fc3749214c76d019fff4e3"><code>77562c3</code></a>
chore: update region comment (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/16380">#16380</a>)</li>
<li><a
href="https://github.com/vitejs/vite/commit/b05c405f6884f9612fd8b6c1e7587a553cf58baf"><code>b05c405</code></a>
fix: <code>fsp.rm</code> removing files does not take effect (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/16032">#16032</a>)</li>
<li><a
href="https://github.com/vitejs/vite/commit/e2658ad6fe81278069d75d0b3b9c260c3021b922"><code>e2658ad</code></a>
perf(css): only replace empty chunk if imported (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/16349">#16349</a>)</li>
<li><a
href="https://github.com/vitejs/vite/commit/c0ec6bea69b6160553f4a5b30652dcef891788fc"><code>c0ec6be</code></a>
perf: reduce size of injected __vite__mapDeps code (<a
href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/16184">#16184</a>)</li>
<li>See full diff in <a
href="https://github.com/vitejs/vite/commits/v5.2.9/packages/vite">compare
view</a></li>
</ul>
</details>
<br />
Updates `tar` from 6.2.1 to 7.0.1
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/isaacs/node-tar/blob/main/CHANGELOG.md">tar's
changelog</a>.</em></p>
<blockquote>
<h1>Changelog</h1>
<h2>7.0</h2>
<ul>
<li>Rewrite in TypeScript, provide ESM and CommonJS hybrid
interface</li>
<li>Add tree-shake friendly exports, like
<code>import('tar/create')</code>
and <code>import('tar/read-entry')</code> to get individual functions or
classes.</li>
<li>Add <code>chmod</code> option that defaults to false, and deprecate
<code>noChmod</code>. That is, reverse the default option regarding
explicitly setting file system modes to match tar entry
settings.</li>
<li>Add <code>processUmask</code> option to avoid having to call
<code>process.umask()</code> when <code>chmod: true</code> (or
<code>noChmod: false</code>) is
set.</li>
</ul>
<h2>6.2</h2>
<ul>
<li>Add support for brotli compression</li>
<li>Add <code>maxDepth</code> option to prevent extraction into
excessively
deep folders.</li>
</ul>
<h2>6.1</h2>
<ul>
<li>remove dead link to benchmarks (<a
href="https://redirect.github.com/isaacs/node-tar/issues/313">#313</a>)
(<a href="https://github.com/yetzt"><code>@yetzt</code></a>)</li>
<li>add examples/explanation of using tar.t (<a
href="https://github.com/isaacs"><code>@isaacs</code></a>)</li>
<li>ensure close event is emited after stream has ended (<a
href="https://github.com/webark"><code>@webark</code></a>)</li>
<li>replace deprecated String.prototype.substr() (<a
href="https://github.com/CommanderRoot"><code>@CommanderRoot</code></a>,
<a
href="https://github.com/lukekarrys"><code>@lukekarrys</code></a>)</li>
</ul>
<h2>6.0</h2>
<ul>
<li>Drop support for node 6 and 8</li>
<li>fix symlinks and hardlinks on windows being packed with
<code>\</code>-style path targets</li>
</ul>
<h2>5.0</h2>
<ul>
<li>Address unpack race conditions using path reservations</li>
<li>Change large-numbers errors from TypeError to Error</li>
<li>Add <code>TAR_*</code> error codes</li>
<li>Raise <code>TAR_BAD_ARCHIVE</code> warning/error when there are no
valid
entries found in an archive</li>
<li>do not treat ignored entries as an invalid archive</li>
<li>drop support for node v4</li>
<li>unpack: conditionally use a file mapping to write files on
Windows</li>
<li>Set more portable 'mode' value in portable mode</li>
<li>Set <code>portable</code> gzip option in portable mode</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/isaacs/node-tar/commit/d99fce38ebf5175cce4c6623c53f4b17d6d31157"><code>d99fce3</code></a>
7.0.1</li>
<li><a
href="https://github.com/isaacs/node-tar/commit/af043922c09d12d28e21ecb463c7c9ff375cbf47"><code>af04392</code></a>
Do not apply linkpath,global from global pax header</li>
<li><a
href="https://github.com/isaacs/node-tar/commit/b0fbdea4631f9f65f15786fb5333695a9164a536"><code>b0fbdea</code></a>
7.0.0</li>
<li><a
href="https://github.com/isaacs/node-tar/commit/957da7506cc594f24f54b884305718927194fb73"><code>957da75</code></a>
remove old lib folder</li>
<li><a
href="https://github.com/isaacs/node-tar/commit/9a260c2dbaf9090c34872944393dfd854940c7c6"><code>9a260c2</code></a>
test verifying <a
href="https://redirect.github.com/isaacs/node-tar/issues/398">#398</a>
is fixed</li>
<li><a
href="https://github.com/isaacs/node-tar/commit/2d89a4edc3dd76aef0bde3a9913cdb4f9c9d3b77"><code>2d89a4e</code></a>
Properly handle long linkpath in PaxHeader</li>
<li><a
href="https://github.com/isaacs/node-tar/commit/314ec7e64245f86663c8ca20fad05ebb5a390d80"><code>314ec7e</code></a>
list: close file even if no error thrown</li>
<li><a
href="https://github.com/isaacs/node-tar/commit/b3afdbb26496fe42110b3708b8f75c4ca4c853b7"><code>b3afdbb</code></a>
unpack test: use modern tap features</li>
<li><a
href="https://github.com/isaacs/node-tar/commit/23304160811cceb1a1949d3915d5a2a818726ec6"><code>2330416</code></a>
test: code style, prefer () to _ for empty fns</li>
<li><a
href="https://github.com/isaacs/node-tar/commit/ae9ce7ec2adb6300155cb6a46f8c9ea601330d81"><code>ae9ce7e</code></a>
test: fix normalize-unicode coverage on linux</li>
<li>Additional commits viewable in <a
href="https://github.com/isaacs/node-tar/compare/v6.2.1...v7.0.1">compare
view</a></li>
</ul>
</details>
<br />
Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore <dependency name> major version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's major version (unless you unignore this specific
dependency's major version or upgrade to it yourself)
- `@dependabot ignore <dependency name> minor version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's minor version (unless you unignore this specific
dependency's minor version or upgrade to it yourself)
- `@dependabot ignore <dependency name>` will close this group update PR
and stop Dependabot creating any more for the specific dependency
(unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore <dependency name>` will remove all of the ignore
conditions of the specified dependency
- `@dependabot unignore <dependency name> <ignore condition>` will
remove the ignore condition of the specified dependency and ignore
conditions
You can disable automated security fix PRs for this repo from the
[Security Alerts page](https://github.com/tldraw/tldraw/network/alerts).
</details>
---------
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Mime Čuvalo <mimecuvalo@gmail.com>
Co-authored-by: Steve Ruiz <steveruizok@gmail.com>
2024-04-21 12:39:38 +00:00
|
|
|
"tar": "^7.0.1",
|
[docs] Sync docs deploy with npm deploy (#3153)
This PR makes it so that our docs deployment process is tied to, and
mirrors, the npm deployment process.
From here on:
- Commits to main get deployed to staging.tldraw.dev
- Commits to a special protected branch called `docs-production` get
deployed to www.tldraw.dev
- Whenever we create a new npm 'latest' release we reset the HEAD of
docs-production to point to the tagged commit for that release.
- If we make a docs change that we want to appear on tldraw.dev ASAP
without waiting for the next npm release, we'll have to follow the same
process as for creating a patch release i.e merge a cherry-pick PR
targeting the latest release branch e.g. `v2.0.x`. This will not cause
another npm patch release unless the cherry-picked changes touch source
files, e.g. updating TSDoc comments.
### Change Type
- [x] `docs` — Changes to the documentation, examples, or templates.
- [x] `tools` — Changes to infrastructure, CI, internal scripts,
debugging tools, etc.
2024-03-14 14:43:32 +00:00
|
|
|
"tmp": "^0.2.3"
|
2023-04-25 11:01:25 +00:00
|
|
|
}
|
|
|
|
|
}
|