React-jss with Next.js style issues

[DMaxence]

I'm using Next.js 14 and I think because of react-jss the styles are not loaded even if I use it in client mode with "use client".

I have in my console this warning :

The classes seems generated but there's no style in it.

I created a sandbox with the bug so you can see https://codesandbox.io/p/devbox/empty-snowflake-td4xnv

[ewan-kerboas]

Same problem here but without use client

[7sne]

Same here

[hxf31891]

Apologies all, CSS & Next has been a persistent issue with this project. I thought JSS would work but apparently not. Regardless will try and get this fixed ASAP.

[nicosh]

Apologies all, CSS & Next has been a persistent issue with this project. I thought JSS would work but apparently not. Regardless will try and get this fixed ASAP.

My i ask you why you choose to use JSS instead of CSS Modules ?

[hxf31891]

@nicosh Next refuses to import style sheets used within npm packages

[nicosh]

@hxf31891 What you mean? You can import external stylesheets without any problem in next.js (as many libraries does). However my question was about CSS modules that are supported natively by react and next without the need of external packages. I've forked the repo and everything work fine by just changing one line of code :

  const useStyles = createUseStyles(styles)
  const classes = useStyles()

with

import styles from '../main.module.css'

[hxf31891]

@nicosh Could you create a PR with your changes please?

[nicosh]

@hxf31891 https://github.com/hxf31891/react-gradient-color-picker/pull/88

I have not tested the final build

[hxf31891]

@nicosh thanks I will test it out

[hxf31891]

Alright I believe this to be fixed in the latest version v3.0.6

Big thanks @nicosh, much appreciated.

I will leave this open for a bit please let me know if the issue persists or others arrive.

One thing to note is that at least for now I removed disableDarkMode which was over complicating things. Will try and bring back in a later release if anybody is using it.

[hxf31891]

@nicosh this should be fixed as of 3.0.10