Add missing READMEs & Update package.json in all RN packages

[Pranav-yadav]

Summary:

This diff adds missing README files for all public RN packages.

Changes:

For all public RN packages:

• Add Missing READMEs

Update package.json in all RN packages to add:

• Issues, Bugs urls
• Keywords and Homepage urls to respective pkgs

Changelog:

[GENERAL][ADDED] - Add missing README files for all public RN packages.
[GENERAL][CHANGED] - Update package.json in all RN packages to add required fields.

Test Plan:

• yarn lint && yarn flow && yarn test-ci --> should be green

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
android	hermes	arm64-v8a	8,499,710	+0
android	hermes	armeabi-v7a	7,833,554	+0
android	hermes	x86	8,977,657	+0
android	hermes	x86_64	8,834,477	+0
android	jsc	arm64-v8a	9,064,270	+0
android	jsc	armeabi-v7a	8,275,566	+0
android	jsc	x86	9,113,565	+0
android	jsc	x86_64	9,374,032	+0

Base commit: b0cf746
Branch: main

[Pranav-yadav]

This PR is stacked on "Update Node.js to v16".

• TODO: Rebase once that PR is merged. Rebased.

Note: I'll be unavailable due to uni. exams, if everything is okay, then please rebase (try slash rebase command) and merge or suggest and commit changes (edits allowed to maintainers) 👍

[Pranav-yadav]

Using symbols like ⚛️ in description is just extra noise for npm and other registries, that too at the start of the descriptions string.
Removing such symbols should make the search easier and should make the packages more accessible.

Same applies for allpackage.json files.

[Pranav-yadav]

git@ (old) & git:// (new) are more prone to attacks than https://.

Due to the lack of TLS or other cryptography, cloning over git://might lead to an arbitrary code execution vulnerability, and should therefore be avoided unless you know what you are doing.

If you run git clone git://example.com/project.git, an attacker who controls e.g your router can modify the repo you just cloned, inserting malicious code into it. If you then compile/run the code you just cloned, you will execute the malicious code. Running git clone http://example.com/project.git should be avoided for the same reason.

Running git clone https://example.com/project.gitdoes not suffer from the same problem (unless the attacker can provide a TLS certificate for example.com). Running git clone [git@example.com]:project.git only suffers from this problem if you accept a wrong ssh key fingerprint.

Reference: https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols
It is very informative read 😃

[Pranav-yadav]

Update: Had some free time, so rebased & resolved the conflicts 😅.

@hoxyq I've left self review above explaining why particular changes are done.
Also about adding more info to respective READMEs, I guess (contributors/maintainers) can iteratively do that as per convenience and shouldn't be a blocker for merging.

cc: @cortinico

[hoxyq]

@cortinico

Are we okay with these keywords?

[Pranav-yadav]

PS. I took them from keyword on RN gh repo page :)

[hoxyq]

What is the purpose of #readme suffix in all these links? Do we want to navigate to README file?

[Pranav-yadav]

Yup, that's the purpose of "homepage" field in case of packages under monorepo, unless we've specific page for each package on RN/any other website.
PS. If you look closely exact similar links are already used in RN packages.

[Pranav-yadav]

Also, #... is just a "fragment" and won't break urls in any case.

[Pranav-yadav]

Rebased & addressed suggestions re: jest testing syntax 👍

[facebook-github-bot]

@hoxyq has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[facebook-github-bot]

@hoxyq merged this pull request in 14316bd.

[Pranav-yadav]

Summary:

This diff adds missing README files for all public RN packages.

Changes:

For all public RN packages:

• Add Missing READMEs

Update package.json in all RN packages to add:

• Issues, Bugs urls
• Keywords and Homepage urls to respective pkgs

Changelog:

[GENERAL][ADDED] - Add missing README files for all public RN packages.
[GENERAL][CHANGED] - Update package.json in all RN packages to add required fields.

Test Plan:

• yarn lint && yarn flow && yarn test-ci --> should be green

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
android	hermes	arm64-v8a	8,499,710	+0
android	hermes	armeabi-v7a	7,833,554	+0
android	hermes	x86	8,977,657	+0
android	hermes	x86_64	8,834,477	+0
android	jsc	arm64-v8a	9,064,270	+0
android	jsc	armeabi-v7a	8,275,566	+0
android	jsc	x86	9,113,565	+0
android	jsc	x86_64	9,374,032	+0

Base commit: b0cf746
Branch: main

[Pranav-yadav]

This PR is stacked on "Update Node.js to v16".

• TODO: Rebase once that PR is merged. Rebased.

Note: I'll be unavailable due to uni. exams, if everything is okay, then please rebase (try slash rebase command) and merge or suggest and commit changes (edits allowed to maintainers) 👍

[Pranav-yadav]

Using symbols like ⚛️ in description is just extra noise for npm and other registries, that too at the start of the descriptions string.
Removing such symbols should make the search easier and should make the packages more accessible.

Same applies for allpackage.json files.

[Pranav-yadav]

git@ (old) & git:// (new) are more prone to attacks than https://.

Due to the lack of TLS or other cryptography, cloning over git://might lead to an arbitrary code execution vulnerability, and should therefore be avoided unless you know what you are doing.

If you run git clone git://example.com/project.git, an attacker who controls e.g your router can modify the repo you just cloned, inserting malicious code into it. If you then compile/run the code you just cloned, you will execute the malicious code. Running git clone http://example.com/project.git should be avoided for the same reason.

Running git clone https://example.com/project.gitdoes not suffer from the same problem (unless the attacker can provide a TLS certificate for example.com). Running git clone [git@example.com]:project.git only suffers from this problem if you accept a wrong ssh key fingerprint.

Reference: https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols
It is very informative read 😃

[Pranav-yadav]

Update: Had some free time, so rebased & resolved the conflicts 😅.

@hoxyq I've left self review above explaining why particular changes are done.
Also about adding more info to respective READMEs, I guess (contributors/maintainers) can iteratively do that as per convenience and shouldn't be a blocker for merging.

cc: @cortinico

[hoxyq]

@cortinico

Are we okay with these keywords?

[Pranav-yadav]

PS. I took them from keyword on RN gh repo page :)

[hoxyq]

What is the purpose of #readme suffix in all these links? Do we want to navigate to README file?

[Pranav-yadav]

Yup, that's the purpose of "homepage" field in case of packages under monorepo, unless we've specific page for each package on RN/any other website.
PS. If you look closely exact similar links are already used in RN packages.

[Pranav-yadav]

Also, #... is just a "fragment" and won't break urls in any case.

[Pranav-yadav]

Rebased & addressed suggestions re: jest testing syntax 👍

[facebook-github-bot]

@hoxyq has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[facebook-github-bot]

@hoxyq merged this pull request in 14316bd.

[Pranav-yadav]

Summary:

This diff adds missing README files for all public RN packages.

Changes:

For all public RN packages:

• Add Missing READMEs

Update package.json in all RN packages to add:

• Issues, Bugs urls
• Keywords and Homepage urls to respective pkgs

Changelog:

[GENERAL][ADDED] - Add missing README files for all public RN packages.
[GENERAL][CHANGED] - Update package.json in all RN packages to add required fields.

Test Plan:

• yarn lint && yarn flow && yarn test-ci --> should be green

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
android	hermes	arm64-v8a	8,499,710	+0
android	hermes	armeabi-v7a	7,833,554	+0
android	hermes	x86	8,977,657	+0
android	hermes	x86_64	8,834,477	+0
android	jsc	arm64-v8a	9,064,270	+0
android	jsc	armeabi-v7a	8,275,566	+0
android	jsc	x86	9,113,565	+0
android	jsc	x86_64	9,374,032	+0

Base commit: b0cf746
Branch: main

[Pranav-yadav]

This PR is stacked on "Update Node.js to v16".

• TODO: Rebase once that PR is merged. Rebased.

Note: I'll be unavailable due to uni. exams, if everything is okay, then please rebase (try slash rebase command) and merge or suggest and commit changes (edits allowed to maintainers) 👍

[Pranav-yadav]

Using symbols like ⚛️ in description is just extra noise for npm and other registries, that too at the start of the descriptions string.
Removing such symbols should make the search easier and should make the packages more accessible.

Same applies for allpackage.json files.

[Pranav-yadav]

git@ (old) & git:// (new) are more prone to attacks than https://.

Due to the lack of TLS or other cryptography, cloning over git://might lead to an arbitrary code execution vulnerability, and should therefore be avoided unless you know what you are doing.

If you run git clone git://example.com/project.git, an attacker who controls e.g your router can modify the repo you just cloned, inserting malicious code into it. If you then compile/run the code you just cloned, you will execute the malicious code. Running git clone http://example.com/project.git should be avoided for the same reason.

Running git clone https://example.com/project.gitdoes not suffer from the same problem (unless the attacker can provide a TLS certificate for example.com). Running git clone [git@example.com]:project.git only suffers from this problem if you accept a wrong ssh key fingerprint.

Reference: https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols
It is very informative read 😃

[Pranav-yadav]

Update: Had some free time, so rebased & resolved the conflicts 😅.

@hoxyq I've left self review above explaining why particular changes are done.
Also about adding more info to respective READMEs, I guess (contributors/maintainers) can iteratively do that as per convenience and shouldn't be a blocker for merging.

cc: @cortinico

[hoxyq]

@cortinico

Are we okay with these keywords?

[Pranav-yadav]

PS. I took them from keyword on RN gh repo page :)

[hoxyq]

What is the purpose of #readme suffix in all these links? Do we want to navigate to README file?

[Pranav-yadav]

Yup, that's the purpose of "homepage" field in case of packages under monorepo, unless we've specific page for each package on RN/any other website.
PS. If you look closely exact similar links are already used in RN packages.

[Pranav-yadav]

Also, #... is just a "fragment" and won't break urls in any case.

[Pranav-yadav]

Rebased & addressed suggestions re: jest testing syntax 👍

[facebook-github-bot]

@hoxyq has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[facebook-github-bot]

@hoxyq merged this pull request in 14316bd.

[Pranav-yadav]

Summary:

This diff adds missing README files for all public RN packages.

Changes:

For all public RN packages:

• Add Missing READMEs

Update package.json in all RN packages to add:

• Issues, Bugs urls
• Keywords and Homepage urls to respective pkgs

Changelog:

[GENERAL][ADDED] - Add missing README files for all public RN packages.
[GENERAL][CHANGED] - Update package.json in all RN packages to add required fields.

Test Plan:

• yarn lint && yarn flow && yarn test-ci --> should be green

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
android	hermes	arm64-v8a	8,499,710	+0
android	hermes	armeabi-v7a	7,833,554	+0
android	hermes	x86	8,977,657	+0
android	hermes	x86_64	8,834,477	+0
android	jsc	arm64-v8a	9,064,270	+0
android	jsc	armeabi-v7a	8,275,566	+0
android	jsc	x86	9,113,565	+0
android	jsc	x86_64	9,374,032	+0

Base commit: b0cf746
Branch: main

[Pranav-yadav]

This PR is stacked on "Update Node.js to v16".

• TODO: Rebase once that PR is merged. Rebased.

Note: I'll be unavailable due to uni. exams, if everything is okay, then please rebase (try slash rebase command) and merge or suggest and commit changes (edits allowed to maintainers) 👍

[Pranav-yadav]

Using symbols like ⚛️ in description is just extra noise for npm and other registries, that too at the start of the descriptions string.
Removing such symbols should make the search easier and should make the packages more accessible.

Same applies for allpackage.json files.

[Pranav-yadav]

git@ (old) & git:// (new) are more prone to attacks than https://.

Due to the lack of TLS or other cryptography, cloning over git://might lead to an arbitrary code execution vulnerability, and should therefore be avoided unless you know what you are doing.

If you run git clone git://example.com/project.git, an attacker who controls e.g your router can modify the repo you just cloned, inserting malicious code into it. If you then compile/run the code you just cloned, you will execute the malicious code. Running git clone http://example.com/project.git should be avoided for the same reason.

Running git clone https://example.com/project.gitdoes not suffer from the same problem (unless the attacker can provide a TLS certificate for example.com). Running git clone [git@example.com]:project.git only suffers from this problem if you accept a wrong ssh key fingerprint.

Reference: https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols
It is very informative read 😃

[Pranav-yadav]

Update: Had some free time, so rebased & resolved the conflicts 😅.

@hoxyq I've left self review above explaining why particular changes are done.
Also about adding more info to respective READMEs, I guess (contributors/maintainers) can iteratively do that as per convenience and shouldn't be a blocker for merging.

cc: @cortinico

[hoxyq]

@cortinico

Are we okay with these keywords?

[Pranav-yadav]

PS. I took them from keyword on RN gh repo page :)

[hoxyq]

What is the purpose of #readme suffix in all these links? Do we want to navigate to README file?

[Pranav-yadav]

Yup, that's the purpose of "homepage" field in case of packages under monorepo, unless we've specific page for each package on RN/any other website.
PS. If you look closely exact similar links are already used in RN packages.

[Pranav-yadav]

Also, #... is just a "fragment" and won't break urls in any case.

[Pranav-yadav]

Rebased & addressed suggestions re: jest testing syntax 👍

[facebook-github-bot]

@hoxyq has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[facebook-github-bot]

@hoxyq merged this pull request in 14316bd.

[Pranav-yadav]

Summary:

This diff adds missing README files for all public RN packages.

Changes:

For all public RN packages:

• Add Missing READMEs

Update package.json in all RN packages to add:

• Issues, Bugs urls
• Keywords and Homepage urls to respective pkgs

Changelog:

[GENERAL][ADDED] - Add missing README files for all public RN packages.
[GENERAL][CHANGED] - Update package.json in all RN packages to add required fields.

Test Plan:

• yarn lint && yarn flow && yarn test-ci --> should be green

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
android	hermes	arm64-v8a	8,499,710	+0
android	hermes	armeabi-v7a	7,833,554	+0
android	hermes	x86	8,977,657	+0
android	hermes	x86_64	8,834,477	+0
android	jsc	arm64-v8a	9,064,270	+0
android	jsc	armeabi-v7a	8,275,566	+0
android	jsc	x86	9,113,565	+0
android	jsc	x86_64	9,374,032	+0

Base commit: b0cf746
Branch: main

[Pranav-yadav]

This PR is stacked on "Update Node.js to v16".

• TODO: Rebase once that PR is merged. Rebased.

Note: I'll be unavailable due to uni. exams, if everything is okay, then please rebase (try slash rebase command) and merge or suggest and commit changes (edits allowed to maintainers) 👍

[Pranav-yadav]

Using symbols like ⚛️ in description is just extra noise for npm and other registries, that too at the start of the descriptions string.
Removing such symbols should make the search easier and should make the packages more accessible.

Same applies for allpackage.json files.

[Pranav-yadav]

git@ (old) & git:// (new) are more prone to attacks than https://.

Due to the lack of TLS or other cryptography, cloning over git://might lead to an arbitrary code execution vulnerability, and should therefore be avoided unless you know what you are doing.

If you run git clone git://example.com/project.git, an attacker who controls e.g your router can modify the repo you just cloned, inserting malicious code into it. If you then compile/run the code you just cloned, you will execute the malicious code. Running git clone http://example.com/project.git should be avoided for the same reason.

Running git clone https://example.com/project.gitdoes not suffer from the same problem (unless the attacker can provide a TLS certificate for example.com). Running git clone [git@example.com]:project.git only suffers from this problem if you accept a wrong ssh key fingerprint.

Reference: https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols
It is very informative read 😃

[Pranav-yadav]

Update: Had some free time, so rebased & resolved the conflicts 😅.

@hoxyq I've left self review above explaining why particular changes are done.
Also about adding more info to respective READMEs, I guess (contributors/maintainers) can iteratively do that as per convenience and shouldn't be a blocker for merging.

cc: @cortinico

[hoxyq]

@cortinico

Are we okay with these keywords?

[Pranav-yadav]

PS. I took them from keyword on RN gh repo page :)

[hoxyq]

What is the purpose of #readme suffix in all these links? Do we want to navigate to README file?

[Pranav-yadav]

Yup, that's the purpose of "homepage" field in case of packages under monorepo, unless we've specific page for each package on RN/any other website.
PS. If you look closely exact similar links are already used in RN packages.

[Pranav-yadav]

Also, #... is just a "fragment" and won't break urls in any case.

[Pranav-yadav]

Rebased & addressed suggestions re: jest testing syntax 👍

[facebook-github-bot]

@hoxyq has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[facebook-github-bot]

@hoxyq merged this pull request in 14316bd.

[Pranav-yadav]

Summary:

This diff adds missing README files for all public RN packages.

Changes:

For all public RN packages:

• Add Missing READMEs

Update package.json in all RN packages to add:

• Issues, Bugs urls
• Keywords and Homepage urls to respective pkgs

Changelog:

[GENERAL][ADDED] - Add missing README files for all public RN packages.
[GENERAL][CHANGED] - Update package.json in all RN packages to add required fields.

Test Plan:

• yarn lint && yarn flow && yarn test-ci --> should be green

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
android	hermes	arm64-v8a	8,499,710	+0
android	hermes	armeabi-v7a	7,833,554	+0
android	hermes	x86	8,977,657	+0
android	hermes	x86_64	8,834,477	+0
android	jsc	arm64-v8a	9,064,270	+0
android	jsc	armeabi-v7a	8,275,566	+0
android	jsc	x86	9,113,565	+0
android	jsc	x86_64	9,374,032	+0

Base commit: b0cf746
Branch: main

[Pranav-yadav]

This PR is stacked on "Update Node.js to v16".

• TODO: Rebase once that PR is merged. Rebased.

Note: I'll be unavailable due to uni. exams, if everything is okay, then please rebase (try slash rebase command) and merge or suggest and commit changes (edits allowed to maintainers) 👍

[Pranav-yadav]

Using symbols like ⚛️ in description is just extra noise for npm and other registries, that too at the start of the descriptions string.
Removing such symbols should make the search easier and should make the packages more accessible.

Same applies for allpackage.json files.

[Pranav-yadav]

git@ (old) & git:// (new) are more prone to attacks than https://.

Due to the lack of TLS or other cryptography, cloning over git://might lead to an arbitrary code execution vulnerability, and should therefore be avoided unless you know what you are doing.

If you run git clone git://example.com/project.git, an attacker who controls e.g your router can modify the repo you just cloned, inserting malicious code into it. If you then compile/run the code you just cloned, you will execute the malicious code. Running git clone http://example.com/project.git should be avoided for the same reason.

Running git clone https://example.com/project.gitdoes not suffer from the same problem (unless the attacker can provide a TLS certificate for example.com). Running git clone [git@example.com]:project.git only suffers from this problem if you accept a wrong ssh key fingerprint.

Reference: https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols
It is very informative read 😃

[Pranav-yadav]

Update: Had some free time, so rebased & resolved the conflicts 😅.

@hoxyq I've left self review above explaining why particular changes are done.
Also about adding more info to respective READMEs, I guess (contributors/maintainers) can iteratively do that as per convenience and shouldn't be a blocker for merging.

cc: @cortinico

[hoxyq]

@cortinico

Are we okay with these keywords?

[Pranav-yadav]

PS. I took them from keyword on RN gh repo page :)

[hoxyq]

What is the purpose of #readme suffix in all these links? Do we want to navigate to README file?

[Pranav-yadav]

Yup, that's the purpose of "homepage" field in case of packages under monorepo, unless we've specific page for each package on RN/any other website.
PS. If you look closely exact similar links are already used in RN packages.

[Pranav-yadav]

Also, #... is just a "fragment" and won't break urls in any case.

[Pranav-yadav]

Rebased & addressed suggestions re: jest testing syntax 👍

[facebook-github-bot]

@hoxyq has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[facebook-github-bot]

@hoxyq merged this pull request in 14316bd.

[Pranav-yadav]

Summary:

This diff adds missing README files for all public RN packages.

Changes:

For all public RN packages:

• Add Missing READMEs

Update package.json in all RN packages to add:

• Issues, Bugs urls
• Keywords and Homepage urls to respective pkgs

Changelog:

[GENERAL][ADDED] - Add missing README files for all public RN packages.
[GENERAL][CHANGED] - Update package.json in all RN packages to add required fields.

Test Plan:

• yarn lint && yarn flow && yarn test-ci --> should be green

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
android	hermes	arm64-v8a	8,499,710	+0
android	hermes	armeabi-v7a	7,833,554	+0
android	hermes	x86	8,977,657	+0
android	hermes	x86_64	8,834,477	+0
android	jsc	arm64-v8a	9,064,270	+0
android	jsc	armeabi-v7a	8,275,566	+0
android	jsc	x86	9,113,565	+0
android	jsc	x86_64	9,374,032	+0

Base commit: b0cf746
Branch: main

[Pranav-yadav]

This PR is stacked on "Update Node.js to v16".

• TODO: Rebase once that PR is merged. Rebased.

Note: I'll be unavailable due to uni. exams, if everything is okay, then please rebase (try slash rebase command) and merge or suggest and commit changes (edits allowed to maintainers) 👍

[Pranav-yadav]

Using symbols like ⚛️ in description is just extra noise for npm and other registries, that too at the start of the descriptions string.
Removing such symbols should make the search easier and should make the packages more accessible.

Same applies for allpackage.json files.

[Pranav-yadav]

git@ (old) & git:// (new) are more prone to attacks than https://.

Due to the lack of TLS or other cryptography, cloning over git://might lead to an arbitrary code execution vulnerability, and should therefore be avoided unless you know what you are doing.

If you run git clone git://example.com/project.git, an attacker who controls e.g your router can modify the repo you just cloned, inserting malicious code into it. If you then compile/run the code you just cloned, you will execute the malicious code. Running git clone http://example.com/project.git should be avoided for the same reason.

Running git clone https://example.com/project.gitdoes not suffer from the same problem (unless the attacker can provide a TLS certificate for example.com). Running git clone [git@example.com]:project.git only suffers from this problem if you accept a wrong ssh key fingerprint.

Reference: https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols
It is very informative read 😃

[Pranav-yadav]

Update: Had some free time, so rebased & resolved the conflicts 😅.

@hoxyq I've left self review above explaining why particular changes are done.
Also about adding more info to respective READMEs, I guess (contributors/maintainers) can iteratively do that as per convenience and shouldn't be a blocker for merging.

cc: @cortinico

[hoxyq]

@cortinico

Are we okay with these keywords?

[Pranav-yadav]

PS. I took them from keyword on RN gh repo page :)

[hoxyq]

What is the purpose of #readme suffix in all these links? Do we want to navigate to README file?

[Pranav-yadav]

Yup, that's the purpose of "homepage" field in case of packages under monorepo, unless we've specific page for each package on RN/any other website.
PS. If you look closely exact similar links are already used in RN packages.

[Pranav-yadav]

Also, #... is just a "fragment" and won't break urls in any case.

[Pranav-yadav]

Rebased & addressed suggestions re: jest testing syntax 👍

[facebook-github-bot]

@hoxyq has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[facebook-github-bot]

@hoxyq merged this pull request in 14316bd.

[Pranav-yadav]

Summary:

This diff adds missing README files for all public RN packages.

Changes:

For all public RN packages:

• Add Missing READMEs

Update package.json in all RN packages to add:

• Issues, Bugs urls
• Keywords and Homepage urls to respective pkgs

Changelog:

[GENERAL][ADDED] - Add missing README files for all public RN packages.
[GENERAL][CHANGED] - Update package.json in all RN packages to add required fields.

Test Plan:

• yarn lint && yarn flow && yarn test-ci --> should be green

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
android	hermes	arm64-v8a	8,499,710	+0
android	hermes	armeabi-v7a	7,833,554	+0
android	hermes	x86	8,977,657	+0
android	hermes	x86_64	8,834,477	+0
android	jsc	arm64-v8a	9,064,270	+0
android	jsc	armeabi-v7a	8,275,566	+0
android	jsc	x86	9,113,565	+0
android	jsc	x86_64	9,374,032	+0

Base commit: b0cf746
Branch: main

[Pranav-yadav]

This PR is stacked on "Update Node.js to v16".

• TODO: Rebase once that PR is merged. Rebased.

Note: I'll be unavailable due to uni. exams, if everything is okay, then please rebase (try slash rebase command) and merge or suggest and commit changes (edits allowed to maintainers) 👍

[Pranav-yadav]

Using symbols like ⚛️ in description is just extra noise for npm and other registries, that too at the start of the descriptions string.
Removing such symbols should make the search easier and should make the packages more accessible.

Same applies for allpackage.json files.

[Pranav-yadav]

git@ (old) & git:// (new) are more prone to attacks than https://.

Due to the lack of TLS or other cryptography, cloning over git://might lead to an arbitrary code execution vulnerability, and should therefore be avoided unless you know what you are doing.

If you run git clone git://example.com/project.git, an attacker who controls e.g your router can modify the repo you just cloned, inserting malicious code into it. If you then compile/run the code you just cloned, you will execute the malicious code. Running git clone http://example.com/project.git should be avoided for the same reason.

Running git clone https://example.com/project.gitdoes not suffer from the same problem (unless the attacker can provide a TLS certificate for example.com). Running git clone [git@example.com]:project.git only suffers from this problem if you accept a wrong ssh key fingerprint.

Reference: https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols
It is very informative read 😃

[Pranav-yadav]

Update: Had some free time, so rebased & resolved the conflicts 😅.

@hoxyq I've left self review above explaining why particular changes are done.
Also about adding more info to respective READMEs, I guess (contributors/maintainers) can iteratively do that as per convenience and shouldn't be a blocker for merging.

cc: @cortinico

[hoxyq]

@cortinico

Are we okay with these keywords?

[Pranav-yadav]

PS. I took them from keyword on RN gh repo page :)

[hoxyq]

What is the purpose of #readme suffix in all these links? Do we want to navigate to README file?

[Pranav-yadav]

Yup, that's the purpose of "homepage" field in case of packages under monorepo, unless we've specific page for each package on RN/any other website.
PS. If you look closely exact similar links are already used in RN packages.

[Pranav-yadav]

Also, #... is just a "fragment" and won't break urls in any case.

[Pranav-yadav]

Rebased & addressed suggestions re: jest testing syntax 👍

[facebook-github-bot]

@hoxyq has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[facebook-github-bot]

@hoxyq merged this pull request in 14316bd.