-
Notifications
You must be signed in to change notification settings - Fork 38
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
Deno compatible #817
Comments
This issue is now marked as stale because it hasn't seen activity for a while. Add a comment or it will be closed soon. If you wish to exclude this issue from being marked as stale, add the "backlog" label. |
keep |
Security is the biggest reason I would love to use Deno over NodeJS. Deno has a secured sandbox that I can trust these types of tools without so much burden. Over and over, NodeJS and NPM packages have proven that it is pretty easy to be vulnerable to malicious actors and that it is quite hard to trust the nightmare of Aside from that, not relying on NPM to be able to use some components is quite a fantastic experience since, in combination with the Deno secured sandbox, you can trust a bit more such imports. I am more than happy to try to make this work with your support, but I am not sure what would be a proper direction here. |
Hey folks, I would like to use the package from Deno, but it uses some NodeJS API
constructs/src/private/uniqueid.ts
Line 1 in ede084c
Is there any opportunity to make this Deno compatible?
The text was updated successfully, but these errors were encountered: