chrome90

[qteamo]

请详细描述您的问题。
f I want to enable support for Chrome 90, what configurations are required to be modified?

[dariamarutkina]

Hello, @qteamo !
Could you please clarify which product you are using and its version?

Also, what exactly happens when you try to use it with Chrome 90?
Do you see any errors or unexpected behavior? If possible, please share screenshots or logs.

[qteamo]

That’s exactly it – the project must run on Chrome 90 exclusively, because the client’s side is on an intranet where only Chrome 90 is available and in use. Currently, we’re facing issues with abnormal page display, broken styling and numerous JS errors. After troubleshooting, I found the root cause: the current Tailwind version is v4, which is not compatible with older browser versions and needs to be downgraded. However, downgrading via plugins alone still won’t work, as many features remain unsupported. So I’m reaching out to ask if there’s a quick and feasible solution to make the project compatible with this older browser version.

[qteamo]

[SychevAndrey]

Hi @qteamo,

CloudBeaver uses Vite and browserslist for browser targeting. Default support is last 3 years of browsers. We do not officially support any older browsers.

Steps to target Chrome 90:

1. Modify browserslist config at webapp/packages/browserslist-config/index.js:
   module.exports = ['Chrome 90', 'not dead'];
2. Install dependencies & build product as usual

Building for Chrome 90 will significantly increase your bundle size with polyfills and likely introduce compatibility issues since CloudBeaver isn't tested against it.
I could not find the official JS Environment Requirements for React 19 that we use, but they were mentioned in the article about the previous version. So, you might need to add a global polyfill.
Many other npm packages assume modern browser support like Tailwind that you mentioned before. I can not guarantee that our bundler will handle all of them.

[EvgeniaBzzz]

Hi @qteamo
Did you manage to modify?