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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing features: arbitrary JS string evaluation (eval() and Function()) #86

Open
samijaber opened this issue Mar 18, 2024 · 3 comments

Comments

@samijaber
Copy link

samijaber commented Mar 18, 2024

I was not able to find this in the list of features, and I know that some do and others don't support it, so it would be good to add it in 馃檹馃徑

@QuiiBz
Copy link
Collaborator

QuiiBz commented Mar 21, 2024

I'm a bit hesitant about this since many cloud providers disable code generation from strings when you actually deploy the code to the cloud - even though it works when you run it locally.

It might be confusing for users to see something marked as supported, but it's not always true depending where the code runs.

@samijaber
Copy link
Author

That's exactly why I think it should be listed as "not supported" for any cloud provider that forbids it on production servers, to differentiate from runtimes like Node that fully support it (and I assume Bun/Deno, although I haven't explicitly checked)

@ascorbic
Copy link
Collaborator

Netlify and Deno Deploy do support it when deployed as well as locally. It would be an annoying one though as it would need lots of special-casing. I'm assuming there isn't a BCD test for it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants