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

Please just add to README about using v3 instead of v4 on unsupported envs #245

Closed
SrBrahma opened this issue Feb 22, 2022 · 3 comments
Closed

Comments

@SrBrahma
Copy link

Please I just lost 4 long and stressful hours today tracking down this issue in my React Native project. It was really awful and couldn't work on what I had to for my contract. I hadn't any info that it was being caused by this lib. The error message I was having didn't give any clue where and what was happening.

I am not asking to change the code, I don't care anymore as I already changed the 4.2.1 to 3.2.1. But be nice to others devs and mention about it on README.

Thanks for the comprehension and feel free to close this after an empathic reflexion.

@Qix-
Copy link
Owner

Qix- commented Feb 22, 2022

I have absolutely no idea what you're talking about. This library doesn't use environment variables.

What error are you referring to?

@SrBrahma
Copy link
Author

By env I mean like React Native environment, not env var.

The enigmatic error I was having was No identifiers allowed directly after numeric literal, with no useful stack trace as I was using isLight on start, and when there are errors on RN startup it messes the stack trace. It was pointing to unrelated java files. It's the famous #222

@Qix-
Copy link
Owner

Qix- commented Feb 22, 2022

with no useful stack

This is a React Native problem, not a problem with this library. Any respectable environment is going to give you adequate error messages to debug a syntax error in a shorter period than 4 hours. Take it up with them, as this is certainly not the last time you're going to run into syntax errors.

I've already done everything I've needed to do to make this library marked properly. It's up to you - not me - to use your tools properly.

@Qix- Qix- closed this as completed Feb 22, 2022
Repository owner locked as resolved and limited conversation to collaborators Feb 22, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants