react-native: RangeError: Maximum call stack size exceeded.

@KPS250 could you provide a reproduction? Also can you try adding sbmodern to the resolvers in metro config like this

module.exports = {
  /* existing config */
  resolver: {
    resolverMainFields: ['sbmodern', 'react-native', 'browser', 'main'],
  },
};

try downgrade corejs

"core-js": "3.23.5",

Can you try setting inline requires to false in your metro config?

Sbmodern resolver only works for storybook 6.5+, try using the 6.5 release candidate with npx sb@next init --type react_native

@CatWithNineLives turning off inline requires shouldn’t be needed anymore in v6.5 you can use the other fix with sbmodern outlined above.

The problem relates to the polyfills being used in storybook core v6 and below (removed in v7).

Probably by turning on inline requires it changes the behaviour of some code. Polyfills usually need to execute first so maybe an import got placed later or removed by the transform.

@hduoc2003 this is because storybook exports multiple different module types (commonjs, esm etc) and sbmodern is a modern output without transpilation.

By putting sbmodern as the first one in the list then we resolve those modules instead of the commonjs output for example.

in the past polyfills from corejs in storybook have caused errors with react native which is why we try to resolve sbmodern

@Mazztwo sbmodern is the fix but it only works on version 6 not on version 5.3.

@osvaguillen thats no longer the suggested fix, you can enable inline requires if you just set the resolvers like I mentioned here:

https://github.com/storybookjs/react-native/issues/405#issuecomment-1436683333

I explained the same issue here: https://github.com/storybookjs/react-native/issues/405#issuecomment-1501154722

The short answer is that polyfilled code from storybook core would break things. We use the resolver config option to resolve a more modern build of storybook core.

@rodgomesc Thank you for sharing, I chose the same way and upgraded to 6.0.1-beta

i’m using this lib for quite a few months, and after my yarn.lock get upgraded in one PR i fall in to that issue, tried to walk through the changes but it was huge and i got lost , after double check everything in documentation it didn’t worked, also compared with https://github.com/dannyhw/expo-storybook-starter everything was in place except for the lib versions, so after use same lib versions as expo-storybook-starter it worked

that’s my diff, hope this work for you as well