#How to Achieve Compatibility with Chrome 61

17 messages · Page 1 of 1 (latest)

vast sequoia
#

astro: 5.7.3

/dist/server/pages/index.astro.mjs

import() need Chrome 63+

primal void
#

Hi! Is there any specific reason you would need to support chrome 61?

vast sequoia
#

According to our device statistics, we have approximately 110000 users with low-level browsers, mostly in Indonesia

#

The main reason is that the default Chrome kernel for Android 8.0 and 7.0 is in version 61-

languid jewelBOT
#

Houston, we have a problem... and <@&1129102257422610512>, you’re our mission control! 🚀

primal void
#

Bit of an interesting one here, I lack the knowledge on Astro. Would be great if someone with experience on this could help!

restive valve
hidden vector
#

Are there any particular js/css features that you use that aren't available <= 61? There are probably work arounds or graceful degredation

Apologies! My point doesn't matter, I reread the error but properly so ignore this

vast sequoia
#

Vite can continue to be backward compatible through @ vitejs/plugin legacy. But it doesn't work for Astro

#

I can use this method in Vite to be compatible with Chrome 62

#

I have checked the packaged file and the content in the client will automatically adapt. But some server rendered JS may not

restive valve
#

Hmm, I don't know what specifically isn't compatible with older chrome versions, but unfortunately we're unlikely to be able to support those versions

rustic gale
#

Yeah I remember trying to use vite plugin legacy like 2 years ago and it was not working already

vast sequoia
#

Will we not spend extra effort on modifying this less critical issue at the moment?
The solution I understand is that server/pages/outer. Astro can determine whether it is an es module or a comjs based on the browser

#

I originally hoped that our app development could have a 70+Chrome kernel browser built into low-end machines

rustic gale