Issue with highcharts, when we have CSS code applied explicitly/implicitly from the pages/_app.js file

[ivan-stojanov]

What version of Next.js are you using?

12.0.7 and 12.0.8-canary.5

What version of Node.js are you using?

16.13.0

What browser are you using?

Chrome

What operating system are you using?

Windows

How are you deploying your application?

next build && next start

Describe the Bug

When using the Next v12.0.7 in combination with "highcharts": "^9.3.2" and "highcharts-react-official": "^3.1.0", in case we want to apply custom styles on the highcharts (with styledMode: true), there is an issue.

The issue is present, only in case we load any CSS code, on app loading. For example: in _app.js, wrap the components under the Layout component and then inside of Layout component, import the Layout.module.css file and apply any class. In case we have any styling applied (in Layout.module.css), after building the project, the overall UI is broken.

During the development, everything works as expected and is not reproducible.
If I downgrade the very same project to Next v11.1, the issue is not present, so this is why I believe the issue is on Next side and not on Highcharts side.

Expected Behavior

We should be able to add CSS code in the components that are loaded via _app.js and this code should not have any impact to the higcharts.

To Reproduce

Get the attached sample project and first run:
npm install

it works well if we use:
npm run dev
and if we visit http://localhost:8082 we will see how it should look like

if we then run
npm run build
npm run start
and if we visit http://localhost:8083 (simulation of the server) we will see how it should look like

here is what us causing it:
if we go at components\Layout.module.css and comment

.delux {
  /*margin: 2px;*/
}

and if we rebuild
npm run build
npm run start
then this will work

This was just a dummy example. To summarize, the issue is reproducible whenever we are directly or indirectly including any CSS code, on page load (via _app.js probably, since the scoped CSS in the components that are not directly loaded from _app.js are not causing the issue).

The current solution is:

• downgrade to Next v11.1

[github-actions]

Please verify that your issue can be recreated with next@canary.

Why was this issue marked with the please verify canary label?

We noticed the provided reproduction was using an older version of Next.js, instead of canary.

The canary version of Next.js ships daily and includes all features and fixes that have not been released to the stable version yet. You can think of canary as a public beta. Some issues may already be fixed in the canary version, so please verify that your issue reproduces by running npm install next@canary and test it in your project, using your reproduction steps.

If the issue does not reproduce with the canary version, then it has already been fixed and this issue can be closed.

How can I quickly verify if my issue has been fixed in canary?

The safest way is to install next@canary in your project and test it, but you can also search through closed Next.js issues for duplicates or check the Next.js releases.

My issue has been open for a long time, why do I need to verify canary now?

Next.js does not backport bug fixes to older versions of Next.js. Instead, we are trying to introduce only a minimal amount of breaking changes between major releases.

What happens if I don't verify against the canary version of Next.js?

An issue with the please verify canary that receives no meaningful activity (e.g. new comments that acknowledge verification against canary) will be automatically closed and locked after 30 days.

If your issue has not been resolved in that time and it has been closed/locked, please open a new issue, with the required reproduction, using next@canary.

I did not open this issue, but it is relevant to me, what can I do to help?

Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps. Furthermore, you can upvote the issue using the 👍 reaction on the topmost comment (please do not comment "I have the same issue" without repro steps). Then, we can sort issues by votes to prioritize.

I think my reproduction is good enough, why aren't you looking into it quicker?

We look into every Next.js issue and constantly monitor open issues for new comments.

However, sometimes we might miss one or two due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.

Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.

Useful Resources

• How to Contribute to Open Source (Next.js)
• How to create a Minimal, Complete, and Verifiable example
• Reporting a Next.js bug
• Next.js Triaging issues

[balazsorban44]

This issue has been automatically closed because it wasn't verified against next@canary. If you think it was closed by accident, please leave a comment. If you are running into a similar issue, please open a new issue with a reproduction. Thank you.

[github-actions]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.