Julien Zapata Duque
Julien Zapata Duque
@gavinhewitt You're right. A couple days ago I found that setting the `sm:max-w-*` classes in the safelist does indeed make them show up. At the time I still had `'./vendor/livewire-ui/modal/resources/**/*'`...
Just checked it on our codebase with `[email protected]` (Node.js version `22.16.0`): running `NODE_OPTIONS="--max-old-space-size=2048" pnpm tsc --noEmit -p tsconfig.test.json` now successfully completes! One thing to note is that adding `--generateTrace ./ts-traces`...
We are experiencing the same issue. We only just now got around to upgrading to v5. We have roughly 20 routes like this that are now broken. Some of these...
Small update: I made a [reproduction](https://github.com/JulienZD/feathers-express-routing-reproduction) which illustrates the routing breaking between v4 and v5. I realized that the hacky workaround I posted in my previous comment doesn't actually work...
Another update: there was an issue with my hacky workaround to pass an empty service, as that causes all requests to that endpoint to first go through all the global...
This is preventing us from upgrading to Refine v5, as it breaks our permission checks in dev. For some reason, the double call to retrieve someone's abilities causes 401s /...