PrivateCoffee/tldraw
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1
tldraw/apps/vscode/editor/package.json

60 lines
1.5 KiB
JSON
Raw Normal View History

transfer-out: transfer out
2023-04-25 11:01:25 +00:00
{
"name": "@tldraw/vscode-editor",
"description": "An an editor for the tldraw vscode extension.",
"version": "2.0.0-alpha.0",
"private": true,
"packageManager": "yarn@3.5.0",
"author": {
"name": "tldraw GB Ltd.",
"email": "hello@tldraw.com"
},
"homepage": "https://tldraw.dev",
"license": "Apache-2.0",
"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"
],
"scripts": {
"build": "yarn run -T tsx scripts/build.ts",
New vite-based examples app (#1226) Right now this examples app looks exactly the same as our old examples app, but there are a couple of tiny differences: - We use `vite` instead of our own esbuild setup for development and bundling - We use `@tldraw/assets` for smart asset hashing instead of copying the assets to a public folder You can use `@tldraw/assets` with vite with a bunch of extra config, but it (plus a bunch of other bundlers) also support a special syntax for specifying asset urls: `new URL('./my/asset.svg', import.meta.url).href`. This approach is more standards-complient, but doesn't work with every bundler just yet. This diff also adds a url-based version of `@tldraw/assets`, although I'd like to tweak the entry point - right now you need to import from `@tldraw/assets/lib/urls`, but i'd like to find a way to get this to `@tldraw/assets/urls` or something at some point. There are a couple other extra fixes in here: - vscode builds were broken, they're fixed now! - there's also a little tweak to the `getBundlerAssetUrls` API to allow passing in a function instead of an object for URL formatting - there are new internal-only functions for injecting asset urls globally instead of passing them in via react props. this means we can get the benefits of cacheable URLs without having to clutter our examples by passing them in
2023-05-05 13:10:36 +00:00
"dev": "yarn run -T tsx scripts/dev.ts",
transfer-out: transfer out
2023-04-25 11:01:25 +00:00
"clean": "rm -rf .turbo && rm -rf node_modules && rm -rf dist",
Revert 09c36781 & tweak linting (#1501) This diff reverts 09c36781 and tweaks how some of our linting was working. I'm not actually sure what caused the regression that 09c36781 was fixing - it was something to do with typescript being used to transpile eslintrc.js, but that being excluded from the tsconfig for those projects. I fixed that by removing `rootDir` from those, but that revealed some other issues with files not getting ignored correctly. I fixed the ignoring issue with a change I've wanted to make to these scripts for a while: only running them on files that are actually tracked by git, instead of on everything with a relevant extension. A side effect of that is that we have to re-implement .eslintignore support ourselves, but that's very straight forward: the `ignore` package that eslint uses is very easy to include. ### Change Type - [x] `internal` — Any other changes that don't affect the published package (will not publish a new version) ### Test Plan - ### Release Notes [internal-only]
2023-06-02 10:45:51 +00:00
"lint": "yarn run -T tsx ../../../scripts/lint.ts"
transfer-out: transfer out
2023-04-25 11:01:25 +00:00
},
"devDependencies": {
"@tldraw/assets": "workspace:*",
"@tldraw/editor": "workspace:*",
"@tldraw/file-format": "workspace:*",
"@tldraw/tldraw": "workspace:*",
"@tldraw/ui": "workspace:*",
"@tldraw/utils": "workspace:*",
"@types/fs-extra": "^11.0.1",
Revert "Update dependencies (#1613)" (#1617) This reverts commit b6716a3750879502dbd9f912e8d19fa37f64a634. Not sure why, but this introduced a `/// <references />` comment in the tldraw/tldraw api-report.md file that doesn't show up when you build from brivate. Reverting for now. ### Change Type - [x] `dependencies` — Changes to package dependencies[^1] ### Test Plan - ### Release Notes -
2023-06-19 09:49:44 +00:00
"@types/node": "^17.0.14",
transfer-out: transfer out
2023-04-25 11:01:25 +00:00
"@types/react": "^18.0.24",
"@types/react-dom": "^18.0.6",
"@types/react-router-dom": "^5.1.8",
Revert "Update dependencies (#1613)" (#1617) This reverts commit b6716a3750879502dbd9f912e8d19fa37f64a634. Not sure why, but this introduced a `/// <references />` comment in the tldraw/tldraw api-report.md file that doesn't show up when you build from brivate. Reverting for now. ### Change Type - [x] `dependencies` — Changes to package dependencies[^1] ### Test Plan - ### Release Notes -
2023-06-19 09:49:44 +00:00
"concurrently": "7.0.0",
transfer-out: transfer out
2023-04-25 11:01:25 +00:00
"create-serve": "1.0.1",
"dotenv": "^16.0.3",
Styles API (#1580) Removes `propsForNextShape` and replaces it with the new styles API. Changes in here: - New custom style example - `setProp` is now `setStyle` and takes a `StyleProp` instead of a string - `Editor.props` and `Editor.opacity` are now `Editor.sharedStyles` and `Editor.sharedOpacity` - They return an object that flags mixed vs shared types instead of using null to signal mixed types - `Editor.styles` returns a `SharedStyleMap` - keyed on `StyleProp` instead of `string` - `StateNode.shapeType` is now the shape util rather than just a string. This lets us pull the styles from the shape type directly. - `color` is no longer a core part of the editor set on the shape parent. Individual child shapes have to use color directly. - `propsForNextShape` is now `stylesForNextShape` - `InstanceRecordType` is created at runtime in the same way `ShapeRecordType` is. This is so it can pull style validators out of shape defs for `stylesForNextShape` - Shape type are now defined by their props rather than having separate validators & type defs ### Change Type - [x] `major` — Breaking change ### Test Plan 1. Big time regression testing around styles! 2. Check UI works as intended for all shape/style/tool combos - [x] Unit Tests - [ ] End to end tests ### Release Notes - --------- Co-authored-by: Steve Ruiz <steveruizok@gmail.com>
2023-06-16 10:33:47 +00:00
"esbuild": "^0.18.3",
transfer-out: transfer out
2023-04-25 11:01:25 +00:00
"fs-extra": "^11.1.0",
update lazyrepo
2023-06-05 17:32:32 +00:00
"lazyrepo": "0.0.0-alpha.27",
[chore] Bump nanoid (#1349) I need to mock nanoid for the ephemeral state fuzz tests, to create repeatable test runs. In order to do that properly it needs to have a consistent version among all our packages. At the same time I'm removing some old unused params in AppOptions ### Change Type <!-- 💡 Indicate the type of change your pull request is. --> <!-- 🤷‍♀️ If you're not sure, don't select anything --> <!-- ✂️ Feel free to delete unselected options --> <!-- To select one, put an x in the box: [x] --> - [ ] `patch` — Bug Fix - [ ] `minor` — New Feature - [x] `major` — Breaking Change - [ ] `dependencies` — Dependency Update (publishes a `patch` release, for devDependencies use `internal`) - [ ] `documentation` — Changes to the documentation only (will not publish a new version) - [ ] `tests` — Changes to any testing-related code only (will not publish a new version) - [ ] `internal` — Any other changes that don't affect the published package (will not publish a new version) ### Release Notes - Remove unused userId and instanceId props from AppOptions
2023-05-11 11:55:00 +00:00
"nanoid": "4.0.2",
transfer-out: transfer out
2023-04-25 11:01:25 +00:00
"react": "^18.2.0",
"react-dom": "^18.2.0",
"tslib": "^2.4.0"
},
"gitHead": "a7dac0f83ad998e205c2aab58182cb4ba4e099a6"
}
Reference in a new issue Copy permalink