lil updates (#724)

* cleanup after yarn

* update comparison

Author: quantizor

.cursorrules

@@ -1 +1,4 @@
-- This project uses yarn package manager.
+- This project uses bun package manager.
+- When debugging, you can directly import index.tsx if using the bun CLI without needing a build step to run experimental scripts.
+- All scripts can be written in TypeScript since Bun handles it natively.
+- Use `bun run test` to run the tests.

.gitignore

@@ -6,14 +6,6 @@ coverage/
 *.log
 package-lock.json
 
-# yarn
-.yarn/*
-!.yarn/patches
-!.yarn/plugins
-!.yarn/releases
-!.yarn/sdks
-!.yarn/versions
-
 # ephemeral files
 dist/
 docs/markdown-to-jsx.js

AGENT.md

@@ -129,9 +129,9 @@ Each markdown element is handled by a rule with this structure:
 
 ### Build Process
 
-1. `yarn build`: uses microbundle, needed for benchmarking
-2. `yarn size`: Automated bundle size checking
-3. `yarn benchmark`: Performance comparison against a recent version of markdown-to-jsx
+1. `bun run build`: uses microbundle, needed for benchmarking
+2. `bun run size`: Automated bundle size checking
+3. `bun run benchmark`: Performance comparison against a recent version of markdown-to-jsx
 
 ## Contributing Guidelines
 

CONTRIBUTING.md

@@ -19,7 +19,7 @@ A good pull request should include a description of the change, any relevant lin
 
 markdown-to-jsx uses semantic versioning. If you're releasing a bugfix, a PATCH version (x.x.X) is sufficient. For new functionality, a MINOR version is warranted (x.X.0). Finally, breaking changes should release a MAJOR version (X.0.0). All maintainers should sign off on breaking changes to ensure they've been thought-through appropriately.
 
-Use the `yarn publish` command to automate the process of building the JS and website, and defining the new version string. Once publish is complete, amend the rebuilt site JS (`git add . && git commit --amend`) and push to main.
+Use the `bun run publish` command to automate the process of building the JS and website, and defining the new version string. Once publish is complete, amend the rebuilt site JS (`git add . && git commit --amend`) and push to main.
 
 Then go to the GitHub Releases panel and add a new one with the same version number. Copy and paste the relevant commits from git history with links to the pull requests and make sure you thank the contributor that added them.
 

bun.lock

@@ -22,7 +22,7 @@
         "jest-serializer-html": "^7.1.0",
         "jest-watch-typeahead": "^2.2.2",
         "markdown-it": "^14.0.0",
-        "markdown-to-jsx-latest": "npm:markdown-to-jsx@7.7.16",
+        "markdown-to-jsx-latest": "npm:markdown-to-jsx@8.0.0",
         "microbundle": "^0.15.1",
         "microtime": "^3.1.1",
         "mkdirp": "^3.0.1",
@@ -1163,7 +1163,7 @@
 
     "markdown-it": ["[email protected]", "", { "dependencies": { "argparse": "^2.0.1", "entities": "^4.4.0", "linkify-it": "^5.0.0", "mdurl": "^2.0.0", "punycode.js": "^2.3.1", "uc.micro": "^2.1.0" }, "bin": { "markdown-it": "bin/markdown-it.mjs" } }, "sha512-a54IwgWPaeBCAAsv13YgmALOF1elABB08FxO9i+r4VFk5Vl4pKokRPeX8u5TCgSsPi6ec1otfLjdOpVcgbpshg=="],
 
-    "markdown-to-jsx-latest": ["markdown-to-jsx@7.7.16", "", { "peerDependencies": { "react": ">= 0.14.0" }, "optionalPeers": ["react"] }, "sha512-2YLPWjSAdJqVCTIQtP3zPPYfLUWuu74Ms7E9vr/RqLTWzPT5clZWNIlgxyzUKD/Gv+P12TNgpnRgtaNNj/vn8A=="],
+    "markdown-to-jsx-latest": ["markdown-to-jsx@8.0.0", "", { "peerDependencies": { "react": ">= 0.14.0" }, "optionalPeers": ["react"] }, "sha512-hWEaRxeCDjes1CVUQqU+Ov0mCqBqkGhLKjL98KdbwHSgEWZZSJQeGlJQatVfeZ3RaxrfTrZZ3eczl2dhp5c/pA=="],
 
     "math-intrinsics": ["[email protected]", "", {}, "sha512-/IXtbwEk5HTPyEwyKX6hGkYXxM9nbj64B+ilVJnC/R6B0pH5G4V3b0pVbL7DBj4tkhBAppbQUlf6F6Xl9LHu1g=="],
 

bunfig.toml

@@ -1,3 +1,3 @@
 [install]
 minimumReleaseAge = 259200 # 3d
-minimumReleaseAgeExcludes = ["markdown-to-jsx-latest"]
+minimumReleaseAgeExcludes = ["markdown-to-jsx"]

notes/FUZZING.md

@@ -5,7 +5,7 @@
 ## Quick Stats
 
 - **36 comprehensive tests**
-- **Run**: `yarn test:fuzz`
+- **Run**: `bun run test:fuzz`
 - **Timeout**: 100ms per test
 - **Categories**: HTML parsing, inline formatting, combined attacks, repetitive delimiters, random fuzzing
 

notes/performance.md

@@ -70,8 +70,8 @@ Every attempt made things slower:
 ## Profiling Tools
 
 ```bash
-yarn profile    # Generate CPU profile
-yarn metrics    # Show parse time, memory, GC stats
+bun run profile    # Generate CPU profile
+bun run metrics    # Show parse time, memory, GC stats
 ```
 
 View profiles in Speedscope or Chrome DevTools Performance tab.

package.json

@@ -78,7 +78,7 @@
     "jest-serializer-html": "^7.1.0",
     "jest-watch-typeahead": "^2.2.2",
     "markdown-it": "^14.0.0",
-    "markdown-to-jsx-latest": "npm:markdown-to-jsx@7.7.16",
+    "markdown-to-jsx-latest": "npm:markdown-to-jsx@8.0.0",
     "microbundle": "^0.15.1",
     "microtime": "^3.1.1",
     "mkdirp": "^3.0.1",