primer/octicons

[Feedback] npm package contains duplicate icon data

xt0rted opened this issue · 16 comments

Describe the topic

I just installed v16.1.1 of @primer/octicons and noticed the svg folder and data.json file are duplicated in the package. I don't think this is intended and it's doubling the size of the package.

image

Hi @xt0rted, thanks for letting us know! We'll take a look at this once we get some open bandwidth.

Hi! This issue has been marked as stale because it has been open with no activity for 180 days. You can comment on the issue or remove the stale label to keep it open. If you do nothing, this issue will be closed in 7 days.

Still an issue in 17.2.0

@jonrohan is this something you might be able to squeeze in this quarter?

Following up, @jonrohan is this still an issue or can we close this?

I think this is still an issue. I believe both data sources are in use, so we'd need to investigate which one we can remove and update any libraries using them.

Hey @JoshBowdenConcepts, this might be a good one to pick up - thoughts?

Hi! This issue has been marked as stale because it has been open with no activity for 180 days. You can comment on the issue or remove the stale label to keep it open. If you do nothing, this issue will be closed in 7 days.

tallys commented

Thank you for raising this issue, it is a known error and is in our backlog.

Would you accept a PR? Sounds like a quick change. This bug doubles the size of the package

https://packagephobia.com/result?p=@primer/octicons@13.0.0

Hi @fregante, thanks for the offer. Yes, we would gladly accept a PR for this change!

Thanks @fregante! ✨ We might be a little slower than usual with PR review due to the holiday season, but we should be able to get to it in the new year. Thanks for contibuting!

This can be closed once #1010 is published to npm. We should see the halving of the package here: https://packagephobia.com/result?p=@primer/octicons

Just wanted to confirm that I don't see this anymore in v19.9.0. Going to close this out as I believe it's been addressed, feel free to leave a comment if I'm getting something wrong here!

Indeed in my link you can see the package going from 2.16 to 1.08, exactly half