Improving site performance by shipping more CSS

 (github.blog)

26 points | by torutofu 18 hours ago

6 comments

  • efortis 12 minutes ago
    There's room for improvement still. Currently, the production build is using long-dev class names. e.g. `DirectoryContent-module__Box_3__gl6dE` could be compiled to a shorter hash like `gl6DE3a2`.

    If you use Vite:

      css: {
    modules: {
      generateScopedName: mode === 'production'
        ? '[hash:base64:8]'
        : '[name]__[local]___[hash:base64:5]',
      }
    }
    [-]
    • Onavo 3 minutes ago
      Would you need a source map then for prod debugging?
  • Gualdrapo 41 minutes ago
    Once (like a year ago or so) stumbled upon some person's post asking for someone to help them to "fix" some section at their website. It was done !important over !important over !important over !important. Said person was really convinced all it needed was another bunch of !important because apparently that was what ai spit for them, at least at that time
  • a11ce 1 hour ago
    Sometimes, [GitHub] posts a [blog post in which they move away from] some terrible [way of doing things] I've never heard before, and it's a weird indirect way to learn how awful their other [design choices] must be.

    https://xkcd.com/2071/

    [-]
  • varun_chopra 30 minutes ago
    Honestly, hats off to them. It's hard to get anything done with Copilot so I'm amazed they even managed to do this.
  • parasti 36 minutes ago
    And yet, there's been a glaring overflow bug on every repo page if the repo has a sponsor button on Firefox Android for months.
  • jay37184 31 minutes ago
    css-in-js? Rofl. Whats next? Html-in-js?
    [-]