client: remove plugin-legacy

Could consider adding it back when vitejs/vite#6535 is merged
SeedTactics · Mar 11, 2022 · 4cd91f8 · 4cd91f8
1 parent a59c280
commit 4cd91f8
Show file tree

Hide file tree

Showing 4 changed files with 4 additions and 39 deletions.
diff --git a/client/insight/package.json b/client/insight/package.json
@@ -53,7 +53,6 @@
     "@types/react-dom": "^17.0.13",
     "@typescript-eslint/eslint-plugin": "^5.14.0",
     "@typescript-eslint/parser": "^5.14.0",
-    "@vitejs/plugin-legacy": "^1.7.1",
     "@vitejs/plugin-react": "^1.2.0",
     "eslint": "^8.10.0",
     "eslint-config-prettier": "^8.5.0",

diff --git a/client/insight/pnpm-lock.yaml b/client/insight/pnpm-lock.yaml
diff --git a/client/insight/vite.config.js b/client/insight/vite.config.js
@@ -2,11 +2,10 @@
 /// <reference types="vite/client" />
 import { defineConfig } from "vite";
 import react from "@vitejs/plugin-react";
-import legacy from "@vitejs/plugin-legacy";
 
 export default defineConfig({
   root: "src",
-  plugins: [react(), legacy({ targets: ["defaults", "not IE 11", "edge 18"] })],
+  plugins: [react()],
   base: "/",
   server: {
     port: 1234,

diff --git a/server/lib/BlackMaple.MachineFramework/http/Startup.cs b/server/lib/BlackMaple.MachineFramework/http/Startup.cs
@@ -187,7 +187,7 @@ public void Configure(
         context.Response.Headers.Add("Content-Security-Policy",
           "default-src 'self'; style-src 'self' 'unsafe-inline'; connect-src *; base-uri 'self'; form-action 'self'; font-src 'self' data:; manifest-src 'self' data:; " +
           // https://github.com/vitejs/vite/tree/main/packages/plugin-legacy#content-security-policy
-          "script-src 'self' 'sha256-tQjf8gvb2ROOMapIxFvFAYBeUJ0v1HCbOcSmDNXGtDo=' 'sha256-MS6/3FCg4WjP9gwgaBGwLpRCY6fZBgwmhVCdrPrNf3E=' 'sha256-T9h4ixy0FtNsCwAyTfBtIY6uV5ZhMeNQIlL42GAKEME='"
+          "script-src 'self';"
         );
         context.Response.Headers.Add("Cross-Origin-Embedder-Policy", "require-corp");
         context.Response.Headers.Add("Cross-Origin-Opener-Policy", "same-origin");