-
Notifications
You must be signed in to change notification settings - Fork 128
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
reduced lib size from 738,548 -> 438,991 #31
Conversation
Signed-off-by: Jasdeep Singh <jasdeepsingh.uppal@gmail.com>
Signed-off-by: Jasdeep Singh <jasdeepsingh.uppal@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work! Repackaging others' work is going to require a few changes, though:
- Each contribution needs to cite the library it was taken from, and have an appropriate license included in the header of the file as a comment, or as a separate LICENSE file.
- All of the source libraries and licenses need to be cited in the project's own README or LICENSE file.
- You need to check that all the licenses allow reuse and modification (they likely do).
- You need to check that the licenses are compatible (eg, they don't have any clauses that prohibit using code under difference licenses together in the same library).
Finally, since this is mostly of use to us, it'd be great if you could transfer the repo and the NPM package to @ensdomains.
package.json
Outdated
@@ -10,6 +10,7 @@ | |||
"lint": "tslint -p tsconfig.json", | |||
"prepare": "npm run build", | |||
"prepublishOnly": "npm run test", | |||
"sized": "browserify src/internal/index.js -p [tsify --noImplicitAny] | wc -c", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the purpose of this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i'll remove it. initially i was planning to use an internal
directory instead of an npm package
package.json
Outdated
"rskjs-util": "^1.0.3", | ||
"stellar-base": "^2.1.2", | ||
"crc": "^3.8.0", | ||
"crypto-addr-codec": "^0.1.1", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please pin this to a specific version?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sure, can i include a yarn.lock file? or just by using the version would be okay?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just using the version is fine.
@Arachnid i'll check with all the packages and see if we can include their license without any issues and i'm more than happy to transfer the ownership of the repo :) |
@inspireme6 sure. can you make a PR to the crypto-addr-serialize repo. I see you've made some changes? |
The only significant change was referencing the shajs modified in the package.json.. I had to add the latest files you uploaded (the stellar files) because they disappeared for some reason (?). The modified shajs package is here https://github.com/inspireme6/sha256js |
@inspireme6 thats my bad, i published it directly from my local work, i didn't push it to the repo. sorry. can you please rebase it from master and update the PR? |
@jay-dee7 I see you have pushed the changes already, it's necessary to rebase it anyways? I'm still new to git, so not sure. |
No its not. I'll do it dont worry 😁 |
@Arachnid i've sent you an invitation for the github repo, please accept it and migrate the repository it to @ensdomains. Since i dont have permissions at ensdomains, i cant transfer. Also, once the repository is migrated, i can un-publish the npm package from my account and you should be able to publish it with the same name or a different one, however you see fit. |
Signed-off-by: Jasdeep Singh <jasdeepsingh.uppal@gmail.com>
@jay-dee7 I now have push access, but you need to add me as an owner before I can transfer it. |
@@ -226,11 +230,8 @@ function b32encodeXemAddr(data: Buffer): string { | |||
} | |||
|
|||
function b32decodeXemAddr(data: string): Buffer { | |||
if(!isValid(data)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This needs to remain in, unless you have something else to check validity.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
adding it right back
Signed-off-by: Jasdeep Singh <jasdeepsingh.uppal@gmail.com>
this validation check put me back in time :( |
@jay-dee7 Thanks, I've accepted the transfer. Are you able to transfer the NPM package to me or to the ensdomains org? |
@Arachnid I'll let you know in next 20 minutes |
@Arachnid i see that both, the repository and the npm package is under @ensdomains organization now. Please let me know if there's something, blocking this PR. |
@Arachnid I just made a PR to the crypto-addr-serialize package that includes the rest of the encoders (bs58 and cashaddr) and includes the sha256 script which was part of the latest changes I made. Also includes the license info for the ss58, cashaddr and shajs packages. After @jay-dee7 PR gets merged, I'll make a PR to this repo that will update the files to include the changes from the updated crypto-addr-serialize package if it goes through. |
reduced lib size from 738,548 -> 438,991
Signed-off-by: Jasdeep Singh jasdeepsingh.uppal@gmail.com