We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
structuredClone
Ships in Node 17
https://nodejs.org/api/globals.html#structuredclonevalue-options https://developer.mozilla.org/en-US/docs/Web/API/structuredClone
it is also used by e.g. worker_threads, which ships from node 10
worker_threads
const envalid = require('envalid'); const config = envalid.cleanEnv({ HELLO: 'foobar' }, { HELLO: envalid.str() }); structuredClone(config);
throws
Uncaught: DOMException [DataCloneError]: #<Object> could not be cloned. at structuredClone (node:internal/structured_clone:15:17)
The text was updated successfully, but these errors were encountered:
Good idea, I hadn't seen this API yet. Any idea how to opt into it? I'm guessing it's the proxy middleware that's problematic here
Sorry, something went wrong.
I don't know if it's possible actually. Seems to be undiscoverable by spec: https://bugzilla.mozilla.org/show_bug.cgi?id=1269327
Should at least add a note in the readme to warn users
Added a Readme note in a new faq section: https://github.com/af/envalid#faq
No branches or pull requests
Ships in Node 17
https://nodejs.org/api/globals.html#structuredclonevalue-options
https://developer.mozilla.org/en-US/docs/Web/API/structuredClone
it is also used by e.g.
worker_threads
, which ships from node 10throws
The text was updated successfully, but these errors were encountered: