From 5ee01433e9b9113845856a052501a766ae18ae00 Mon Sep 17 00:00:00 2001
From: Dmitry Sharabin <dmitrysharabin@gmail.com>
Date: Tue, 2 Jun 2026 23:50:08 +0200
Subject: [PATCH] Remove obsolete jspm config from package.json

The `jspm` field dates from JSPM 0.x/1.x and references paths that no
longer exist (`prism.js` at root, `components/`, `plugins/`, `themes/`
at root). Modern JSPM reads the standard `exports` field, which already
maps all entry points correctly.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---
 package.json | 12 ------------
 1 file changed, 12 deletions(-)

diff --git a/package.json b/package.json
index 866e7b7449..38e0447af0 100644
--- a/package.json
+++ b/package.json
@@ -112,17 +112,5 @@
 		"typescript": "^5.8.3",
 		"webfont": "^11.2.26",
 		"yargs": "^17.7.2"
-	},
-	"jspm": {
-		"main": "prism",
-		"registry": "jspm",
-		"jspmPackage": true,
-		"format": "global",
-		"files": [
-			"components/**/*.js",
-			"plugins/**/*",
-			"themes/*.css",
-			"prism.js"
-		]
 	}
 }