Git Product home page Git Product logo

Comments (7)

joehiggs avatar joehiggs commented on June 12, 2024

+1

from emoji-data.

timabbott avatar timabbott commented on June 12, 2024

I'd also find this useful, since it makes it easier to keep track of when new releases are available without having to check manually.

from emoji-data.

iamcal avatar iamcal commented on June 12, 2024

it's currently broken because the package (just with the spritesheets, not the individual images) are too large :(

from emoji-data.

iamcal avatar iamcal commented on June 12, 2024

my plan it to break it up into multiple packages, one per image set

from emoji-data.

jamesplease avatar jamesplease commented on June 12, 2024

@iamcal have you considered merging all of these projects into a monorepo? The benefits that you may see would be:

  • no sub modules, which is ever-so-slightly less complexity
  • everything in one place makes it easy to rearrange files for publishing to npm
  • tools like lerna can make tasks like building/testing/publishing into a single command

I know you've mentioned in the past that you don't use npm, so I can imagine how it might be frustrating to have to manage all of these different packages if there are many steps to doing a release. If you think that could be the case, then a monorepo could be worth looking into. If you've got some other plan to automate it, or don't think the work will be too much, then no worries.

I really appreciate that you're doing this, by the way! Thank you!

from emoji-data.

iamcal avatar iamcal commented on June 12, 2024

I assume you mean this repo and the JS one? There are about 10 different language versions which rely on this datasource, only some of which are by me, so I don't have the option to merge.

Beyond that, the problems with publishing to npm are:

  • The whole emoji-data report is just too big for npm
  • npm does not give you an easy way to publish multiple packages from a single repo (i'm scripting that now)
  • I constantly hit a 2+ year old npm bug which means publishing fails due to a stack overflow (the only advice in the issue threads is to not use npm!)

I'm close to having one base package on npm (with minimal images), plus one per image set which contains everything. If I can get around the stack overflow problems, it'll be done.

from emoji-data.

iamcal avatar iamcal commented on June 12, 2024

v2.5.2 is now on npm. More details here: https://github.com/iamcal/emoji-data#installation

from emoji-data.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.