Michael Trachtman

Nope, I believe as long as you ensure `custom.semantic.json` is in a `/client` folder relative to your `meteor` folder you should be good. My setup is done exactly as recommended...

Thank you @klausklapper for following up here. @flemay @jlukic any guidance you could provide to the community would be greatly appreciated. We'd looooove to see a new version up on...

If the approach could allow us to use LESS to override some of the core CSS values (like colors and typography) I think that's mostly good enough. Perhaps secondarily since...

There are some recommendations out there to [move Semantic-UI into its own local package to keep build times down](https://medium.com/@lucashansen/faster-meteor-reloads-62cca5b56460#.q15bmnfd7). > Move as much of your code as possible into many...

Potentially related to https://github.com/c3js/c3/issues/1527.

I was able to work around this issue by specifying use of the [classic runtime option](https://github.com/vitejs/vite/tree/main/packages/plugin-react#opting-out-of-the-automatic-jsx-runtime) for `@vitejs/plugin-react`, making a change to `vite.config.js`, though presumably it would be ideal to...

The initial workaround (use Vite 2; no support for Vite 3 at the time) and now the latest plugin beta and Vite 3 have cleared up the original issue for...

Seems reasonable; I think there are some other issues that have been closed under similar circumstances (including a related one I just closed but maybe shouldn't have). Maybe we just...

I ran into this as well on an Intel MacBook Pro - I just wanted to upgrade pnpm to the latest version (to 7.27.1), so I tried running the `curl...

I continue to run into this time to time when I upgrade - it happened again when running an upgrade from 7.30.1 to 7.30.3. No good workaround on macOS (Intel)...