Fix #20622: Make custom aliases work in both dev and production

[alilo113]

Problem

In development mode, custom aliases like $broke:/ were not resolved correctly, causing import errors. In production, the aliases worked fine.

Solution

• Removed the colon / from the alias names ($broke:/ → $broke, $okay:/ → $okay)
• Updated imports to match the new aliases
• Verified that both dev and production builds correctly resolve the aliases

This ensures consistent behavior across dev and production environments.

import { defineConfig } from "vite";
import path from "node:path";

export default defineConfig({
  resolve: {
    alias: [
      { find: "$okay", replacement: path.resolve(__dirname, "src") },
      { find: "$broke", replacement: path.resolve(__dirname, "src") },
    ],
  },
});