Skip to content

docs: add disclaimer about NodeJS usage#16

Merged
shivam-deepsource merged 3 commits intomasterfrom
shivam-deepsource-patch-2
Feb 24, 2022
Merged

docs: add disclaimer about NodeJS usage#16
shivam-deepsource merged 3 commits intomasterfrom
shivam-deepsource-patch-2

Conversation

@shivam-deepsource
Copy link
Copy Markdown
Contributor

No description provided.

@tusharsadhwani
Copy link
Copy Markdown

tusharsadhwani commented Feb 24, 2022

Is it possible to use node's crypto APIs in place of web's when running on node, just to make it work everywhere?

Comment thread README.md Outdated
@yash-deepsource
Copy link
Copy Markdown
Member

Is it possible to use node's crypto APIs in place of web's when running on node, just to make it work everywhere?

Considering this option, will get back to you!

@shivam-deepsource
Copy link
Copy Markdown
Contributor Author

Is it possible to use node's crypto APIs in place of web's when running on node, just to make it work everywhere?

Currently, we intended for it to be browser only. To be used internally on the frontend app, we can allow node usage if we need it.

The original rationale was that NodeJS is a more controlled environment, developers already know what APIs are available to them, unlike the browser. One can simply use crypto.randomBytes(100).toString('base64'); to generate the secret or use something like nanoid

@shivam-deepsource shivam-deepsource merged commit 6f9c873 into master Feb 24, 2022
@shivam-deepsource shivam-deepsource deleted the shivam-deepsource-patch-2 branch February 24, 2022 11:17
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

Successfully merging this pull request may close these issues.

3 participants