Per Svensson

I had the same problems, removing the unnessesary preprosessor karma-babel-preprocessor from packages.json (and removing the files in node_modules ofc) made everythign work again. Iv´e been trying to debugg and replicate...

@Bretto, confirmed. Changing path to local Karma solves the issue.

3.3.20 had this issue as well, i observed that the "stuck in loading" was only true when i provided the onCompleted cb 3.5.5 (latest at the time of writing) fixed...

The confusing babel output. ``` exports.default = _Modal2.default; module.exports = exports['default']; ``` Not using defaults just makes the world a happier place, without a default people can still just rename...

I started to look at this but i can't get my fork to run on my machine. The build can't access Microsoft.CodeAnalysis.CSharp even though it's clearly there and everything is...

@noru Did you find a workaround other than manually copy/past the styles inside the shadow?

Using the chat: Me: @workspace Help me to mock myFunction in the test? CP: To mock myFunction function, you can use a mocking library like jest. Here's how you can...

This PR does NOT contain Tests Updated doc. It was created as a discussion point, if you think this is a valid approach i can update the PR to include...

Just to confirm, the vite.config.ts loaded and used by default. Work fine to set react > babel config there Im currently using storybook 7.0.0-beta.19

Another workaround to get people going with node 18. Using swa 1.1.1 and Node 18.12.1 i was able to get everything to work as expected with `swa start --host=127.0.0.1 --port=3010...