Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parcel's polyfill issue #3059

Closed
tuoxiansp opened this issue Feb 4, 2023 · 4 comments
Closed

Parcel's polyfill issue #3059

tuoxiansp opened this issue Feb 4, 2023 · 4 comments
Labels
bug Something isn't working

Comments

@tuoxiansp
Copy link

tuoxiansp commented Feb 4, 2023

Describe the issue

Our project are facing some compatibility problem with Logto. It was caused by parcel's polyfill issue

see: Parcel does not include polyfill for older browsers even when browserslist is declared in the package.json

Parcel doesn't include any polyfill at all, even though browserslist is declared in the package.json.

An effective workaround just for us was patching logto and import core-js from the entry point;


edit:

Describe the bug

Got white screen on some Android device when user login.
We have 200+ users for now. There were at least 10 users got the white screen problem.
It was caused by the unsupported Object.fromEntries when I reproduced this on Chrome 66.

Expected behavior

User can open login page.

How to reproduce?

Login on Chrome 66.

Context

OS:

Environment:
Docker

Logto version:
v1.0.0-beta.19

Node version:
v16

Postgres version:
v15

Command of starting Logto:
npm start

Screenshots

I'm sorry cannot provide screenshot here because it was fixed already with some workaround.

@tuoxiansp tuoxiansp added the bug Something isn't working label Feb 4, 2023
@gao-sun
Copy link
Member

gao-sun commented Feb 4, 2023

can you follow the template to provide more context?

@tuoxiansp
Copy link
Author

tuoxiansp commented Feb 5, 2023

can you follow the template to provide more context?

done.

@gao-sun
Copy link
Member

gao-sun commented Feb 6, 2023

@tuoxiansp thanks! Chrome 66 is old enough as it was published on April, 2018. but this reminds us to test browser compatibility and mark it on the docs

@gao-sun
Copy link
Member

gao-sun commented Feb 9, 2023

opened #3079 for convenience. close the issue since there's nothing Logto can do to fix

@gao-sun gao-sun closed this as not planned Won't fix, can't repro, duplicate, stale Feb 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

No branches or pull requests

2 participants