Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Remove lodash and use our own utils#535

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
itsmichaeldiego merged 7 commits intomasterfromremove-lodash-use-our
Mar 12, 2018

Conversation

itsmichaeldiego
Copy link
Member

@itsmichaeldiegoitsmichaeldiego commentedMar 12, 2018
edited
Loading

This PR is just one proposal to use specific packages from lodash instead of importing the whole library.

I came across with the problem that we tried to remove lodash here:670fadd#diff-b9cfc7f2cdf78a7f4b91a753d10865a2R72 but we actually moved to devDependencies.

But accidentally, because it was there,@ZAKdev usedfp from lodash, as it was still in the devdependencies, in#441.

After that, I also used isEmpty from lodash in#533

This increased the build size to 797kb standard and 201kb minified.

This PR decreases it to 140kb and 47.5kb minified.

Output: Size decreased by almost 4 times.

Prev:

screen shot 2018-03-11 at 2 00 52 pm

Now:

screen shot 2018-03-11 at 7 43 57 pm

@itsmichaeldiegoitsmichaeldiego changed the titleRemove lodash use ourRemove lodash use our own librariesMar 12, 2018
@itsmichaeldiego
Copy link
MemberAuthor

itsmichaeldiego commentedMar 12, 2018
edited
Loading

@ZAKdev Let me know if this change works with your heatmaps. I would really prefer you to make a PR on its own but I can go either way.

@itsmichaeldiegoitsmichaeldiego changed the titleRemove lodash use our own librariesRemove lodash and use our own librariesMar 12, 2018
@itsmichaeldiegoitsmichaeldiego changed the titleRemove lodash and use our own librariesRemove lodash and use our own utilsMar 12, 2018
option => instance.set(option, options[option]),
Object.keys(options || {})
);
Object.keys(options).map(option => instance.set(option, options[option]));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I don't know why but i am not able to run entire project, so everything looks good to me just map over an empty object as well if there is no options, like below.

Object.keys(options || {}).map(option => instance.set(option, options[option]));

Copy link
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

@ZAKdev Done, instead of doing what you said I've set a default value for the parameter. LMK How that works. I am merging this as for now.

@ZAKdev
Copy link
Contributor

This is what i am getting from every branch.

screen shot 2018-03-12 at 19 35 13

itsmichaeldiego reacted with thumbs up emoji

@itsmichaeldiego
Copy link
MemberAuthor

@ZAKdev Fixed this in#537, you should be looking good now, please start fromlatest master

@itsmichaeldiegoitsmichaeldiego merged commit8cb6939 intomasterMar 12, 2018
@itsmichaeldiegoitsmichaeldiego deleted the remove-lodash-use-our branchMarch 12, 2018 22:56
@ZAKdev
Copy link
Contributor

@itsmichaeldiego, i can't push any of my code, seems like not having access.

@itsmichaeldiego
Copy link
MemberAuthor

@ZAKdev sorry, push to where?

@ZAKdev
Copy link
Contributor

@itsmichaeldiego, i added weight in my heapmap implementation but i am not able to push my code to this repo.

Do we have any slack channel where we can comminicate or via email, here is my emailzainahmedkhan@gmail.com

@lock
Copy link

lockbot commentedDec 1, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@locklockbot locked asresolvedand limited conversation to collaboratorsDec 1, 2019
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Reviewers

@ZAKdevZAKdevZAKdev left review comments

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

2 participants
@itsmichaeldiego@ZAKdev

[8]ページ先頭

©2009-2025 Movatter.jp