Ryan Bower
Not entirely sure. The example that I included is close to minimal.
You may also need to enable strict mode in your tsconfig. The errors sometimes don't show when `strict` is set to false.
@ianstormtaylor hosted a reproduction of the error at https://github.com/R-Bower/superstruct-describe-error-reproduction
@voycey Did you enable the profile in the right click context menu?  I also enabled `force_disable_primary` in the `general` section of the settings. This is working for me.
Link to fix: https://github.com/TanStack/table/issues/3965#issuecomment-1912872932
For anybody still looking for a solution here, I've managed to combine [cssnano](https://cssnano.co/) and [postcss-lightningcss](https://github.com/onigoetz/postcss-lightningcss) to achieve the desired result. Note that this will require postcss.
@khuezy I've tried to replicate the nextjs deployment but am seeing some build errors. Tried to join the discord but the link you provided takes me to a broken server.
> @R-Bower hey just wanted to check did you manage to find any solution ? Thanks I went with @khuezy's recommendation and that's been working well for me.
+1 on this. I'm in a similar situation.
Managed to fix this by modifying Next's webpack config. The solution is to force webpack to use the babel config for the NestJS code. ``` // in next.config.js webpack: (config)...