typeslayer 0.1.7 → 0.1.8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +19 -5
- package/package.json +5 -7
package/README.md
CHANGED
|
@@ -28,22 +28,36 @@ in the root package you want to inspect (i.e. colocated to your package.json). T
|
|
|
28
28
|
- will this support monorepos?
|
|
29
29
|
- that's the hope. one step at a time.
|
|
30
30
|
- why isn't this just a CLI tool?
|
|
31
|
-
-
|
|
32
|
-
- I don't like CLI tools. I view them as a last resort, at this point in engineering history.
|
|
31
|
+
- a goal of the project is show intuitive/beautiful interactive visualizations like treemaps and force graphs, inherently not something a terminal can provide.
|
|
32
|
+
- I don't like CLI tools. I view them as a last resort, at this point in engineering history. if you're someone that stays up late into the night staring at your dotfiles from neovim... I'm happy for you. be happy for me too?
|
|
33
33
|
- will this work with ts-go?
|
|
34
34
|
- that's the hope but it ain't ready yet on the ts-go side
|
|
35
35
|
|
|
36
|
+
# Who needs this stupid thing, anyway?
|
|
37
|
+
|
|
38
|
+
TypeSlayer is one of those things that most developers don't need. others might just find it lulzy to play around with.
|
|
39
|
+
|
|
40
|
+
but then there's the power users. the library authors. the people attending SquiggleConf. you know the kind.
|
|
41
|
+
|
|
42
|
+
for the people pushing the boundaries of TypeScript (or at companies doing so intentionally or not), a tool like this is something we haven't seen before. there were ways to trash _hours_ messing with multi-hundred-megabyte JSON files. and that's not even counting the time required to learn how the TypeScript compiler works so you can understand the problem... it's a lot.
|
|
43
|
+
|
|
44
|
+
consider the fact that this can sometimes feel like an impossible task for a library author because the code that actually exercises the library isn't directly accessible - it's in the _library user_'s code (which is usually private).
|
|
45
|
+
|
|
46
|
+
I made TypeSlayer because I learned delulu-levels-of-detail about TypeScript performance tuning [while getting Doom to run in TypeScript types](https://youtu.be/0mCsluv5FXA), yet many of those techniques are still opaque to most people.
|
|
47
|
+
|
|
48
|
+
I wanted to make it easy for others to put up PRs at their companies all like "I increased type-checking perf on this file by 380,000x and shaved 23 seconds off every CI run" (real story btw lol). I took what I learned about how to debug type performance and wrapped it all up into this tool.
|
|
49
|
+
|
|
36
50
|
## Data / Security
|
|
37
51
|
|
|
38
52
|
TypeSlayer supports Linux x64, macOS x64 (Intel), macOS ARM64 (Apple Silicon), and Windows x64. Please note that next year is the year of the Linux desktop.
|
|
39
53
|
|
|
40
|
-
TypeSlayer currently does not collect any analytics - although it probably will try to collect "someone somewhere ran it at XYZ timestamp" data in the future.
|
|
54
|
+
TypeSlayer currently does not collect any analytics - although it probably will try to collect "someone somewhere ran it at XYZ timestamp" data in the future. all data is stored:
|
|
41
55
|
|
|
42
56
|
- Linux: `~/.local/share/typeslayer/`
|
|
43
57
|
- macOS: `~/Library/Application Support/typeslayer/`
|
|
44
58
|
- Windows: `%APPDATA%\typeslayer\`
|
|
45
59
|
|
|
46
|
-
|
|
60
|
+
TypeSlayer can read any file the running user can read and it can run package.json scripts (so treat it as you would your terminal).
|
|
47
61
|
|
|
48
62
|
## Contributing
|
|
49
63
|
|
|
@@ -52,4 +66,4 @@ This tool can read any file the running user can read and it can run package.jso
|
|
|
52
66
|
|
|
53
67
|
## Thank You
|
|
54
68
|
|
|
55
|
-
|
|
69
|
+
this app is built with Tauri, TanStack, Vite, Biome, React, MUI, Rust, and of course, TypeScript.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "typeslayer",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.8",
|
|
4
4
|
"description": "Slay your TypeScript types",
|
|
5
5
|
"private": false,
|
|
6
6
|
"type": "module",
|
|
@@ -40,16 +40,14 @@
|
|
|
40
40
|
"arm64"
|
|
41
41
|
],
|
|
42
42
|
"engines": {
|
|
43
|
-
"node": ">=24.0.0"
|
|
44
|
-
"pnpm": ">=10.0.0"
|
|
43
|
+
"node": ">=24.0.0"
|
|
45
44
|
},
|
|
46
|
-
"packageManager": "pnpm@10.6.5",
|
|
47
45
|
"scripts": {
|
|
48
46
|
"postinstall": "node scripts/postinstall.js"
|
|
49
47
|
},
|
|
50
48
|
"optionalDependencies": {
|
|
51
|
-
"@typeslayer/linux-x64": "0.1.
|
|
52
|
-
"@typeslayer/darwin-arm64": "0.1.
|
|
53
|
-
"@typeslayer/win32-x64": "0.1.
|
|
49
|
+
"@typeslayer/linux-x64": "0.1.8",
|
|
50
|
+
"@typeslayer/darwin-arm64": "0.1.8",
|
|
51
|
+
"@typeslayer/win32-x64": "0.1.8"
|
|
54
52
|
}
|
|
55
53
|
}
|