Addon storybook-core-core-server-presets-0 not loaded in CI build, but present in local "production" build

[yuri-scarbaci-lenio]

We're encountering an issue with our Storybook build in the Jenkins environment. The final manager-bundle.js doesn't load storybook-core-core-server-presets-0 before other addons, which causes unexpected behavior.

Interestingly, the same codebase produces a manager-bundle.js that loads storybook-core-core-server-presets-0 correctly when run locally or in environments like StackBlitz, as expected.

I've been trying to isolate any differences between the Jenkins build and local environments but haven't found anything conclusive. We haven't made any relevant changes that could affect this behavior.

Could anyone point out potential causes or differences that might be influencing this? From what I understand, addon loading should only be controlled via the main.js configuration, and the main.js file is identical between local development and the Jenkins build process.

Any insights would be greatly appreciated!

Additional Information

The configuration is equivalent to the setup in this StackBlitz example.

Not loading the addon breaks the portal completely because the addon in question is responsible for correctly initializing the hooks for other addons. As a result, the portal crashes with the following error:

Uncaught TypeError: Cannot read properties of undefined (reading 'getGlobals')
    at useGlobals

When inspecting the source -> sb-addons output from the mounted artifact, the issue is evident:

(Addons 4 to 10 are custom addons developed specifically for our portal. However, including or excluding these custom addons doesn't affect the outcome—the storybook-core-core-server-presets-0 addon still doesn't load correctly in the Jenkins build, even though it works in other environments.)

I am currently verifying whether this issue is specific to a Storybook version, this has been observed in version 8.4.5.
I'll post an update once I confirm whether version 8.2.9 (which is the version we were using before encountering this issue) works as expected.

Create a reproduction

this is our storybook setup but it can't be reproduced in stackblitz

[yuri-scarbaci-lenio]

downgrading to 8.2.9 results in the storybook-core-core-server-presets-0 to be correctly loaded, but now for some reason (without changes on our side that I am aware of, nor any discrepancies I am able to detect between the jenkins CI and local setups that should be impacting this) we still can't get the portal to load

and out of the blue we are hit with

hook.js:608 Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem. Error Component Stack
    at manager-bundle.js:11:433

related manager bundle line:

which finally critically fails at

Uncaught TypeError: Cannot read properties of null (reading 'useRef')
    at useRef (globals-runtime.js:842:16)
    at usePrevious (globals-runtime.js:48725:25)
    at useUpdate (globals-runtime.js:48730:11)
    at AddonPanel (globals-runtime.js:48734:67)
    at renderWithHooks (chunk-NFZCBIX3.js:83:936)
    at mountIndeterminateComponent (chunk-NFZCBIX3.js:83:57790)
    at beginWork (chunk-NFZCBIX3.js:85:20861)
    at HTMLUnknownElement.callCallback2 (chunk-NFZCBIX3.js:16:1922)
    at Object.invokeGuardedCallbackDev (chunk-NFZCBIX3.js:16:2446)
    at invokeGuardedCallback (chunk-NFZCBIX3.js:16:3704)

I am not sure if #27005 is related or not, but it looks like something broke in the storybook UI build process and I am not even able to reproduce it in my local environment

[yuri-scarbaci-lenio]

This is a better reproduction of our setup,
still no luck understanding what could be going wrong exclusively in the CI environment with this setup

[yuri-scarbaci-lenio]

We found the solution, it was a mix of how the .npmrc flags works with pnpm and some peculiar configuration of our CI env not correctly solving the storybook version in our build environment