Skip to content

Unleash NextJS not working on old browser like Chrome v50 #173

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

Closed
chenxeed opened this issue Aug 6, 2024 · 2 comments
Closed

Unleash NextJS not working on old browser like Chrome v50 #173

chenxeed opened this issue Aug 6, 2024 · 2 comments
Assignees

Comments

@chenxeed
Copy link

chenxeed commented Aug 6, 2024

Describe the bug

Hi! 👋

Firstly, thanks for your work on this project! 🙂

I have an issue on trying to use unleash on my client side.

I'm supporting old browser up to Chrome v50, and I got an error that the page cannot load due to the usage of async await in the updateContext:

image

Screenshot 2024-08-06 190448

Steps to reproduce the bug

  1. Use @unleash/nextjs which also rely on @unleash/proxy-client-react
  2. Build the app in nextJS
  3. Open the app in old browser like Chrome v50

Expected behavior

No unsupported syntax on old browser that triggers error.

Logs, error output, etc.

Uncaught SyntaxError: Unexpected identifier

Screenshots

image

Screenshot 2024-08-06 190448

Additional context

No response

Unleash version

v4.3.0

Subscription type

Open source

Hosting type

Self-hosted

SDK information (language and version)

frontend SDK

@gastonfournier
Copy link

Hi @chenxeed thanks for the issue and the contribution! We'll look into it!

@Tymek Tymek removed the bug Something isn't working label Aug 7, 2024
@gastonfournier gastonfournier self-assigned this Aug 30, 2024
@Tymek
Copy link
Member

Tymek commented Feb 5, 2025

We’re aware that older browsers might face issues, but we’re focusing our efforts on current versions. Chrome 50 is nearly 9 years old and should not be used due to security concerns. If you need modifications for older browsers, feel free to fork the repository and adjust the code. Thank you for your understanding.

@Tymek Tymek closed this as not planned Won't fix, can't repro, duplicate, stale Feb 5, 2025
@github-project-automation github-project-automation bot moved this from In Progress to Done in Issues and PRs Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants