Find a file
2025-03-10 01:05:12 -04:00
.vscode hey look a thing 2025-03-10 00:02:54 -04:00
syntaxes uhh i guess just add the built files for now 2025-03-10 01:00:55 -04:00
.gitignore hey look a thing 2025-03-10 00:02:54 -04:00
base.package.json npm run build should maybe actually work 2025-03-10 01:05:12 -04:00
build.mts hey look a thing 2025-03-10 00:02:54 -04:00
dprint.json hey look a thing 2025-03-10 00:02:54 -04:00
embeddedLanguages.mts add support for embedded language aliases 2025-03-10 00:59:09 -04:00
grammar.mts put all the type definitions in the same place 2025-03-10 00:58:38 -04:00
package-lock.json npm run build should maybe actually work 2025-03-10 01:05:12 -04:00
package.json npm run build should maybe actually work 2025-03-10 01:05:12 -04:00
package.json.mts hey look a thing 2025-03-10 00:02:54 -04:00
README.md npm run build should maybe actually work 2025-03-10 01:05:12 -04:00
util.mts add helper for assembling long scope lists 2025-03-10 00:59:26 -04:00

embedded-string-highlighting

textmate grammars can't be that bad right??

how the fuck

npx tsx build.mts to turn *.json.mts files into *.json files which are actually used by the extension. yes package.json is autogenerated by injecting vs code's extension contribution point nonsense into the contents of the existing base.package.json file. yes it's terrible. no i probably won't ever bother separating the source files from the built output, that sounds complicated