Code Monkey home page Code Monkey logo

Comments (4)

ruyadorno avatar ruyadorno commented on July 20, 2024

Build and test

  • Keep datauri module and datauri-cli on a single monolithic repo using lerna.js instead of current code, or split them in 2 github projects?

While Lerna is raising in popularity for larger projects, for the "lib + cli" case trend seems to go the other way these days. I think most people like having separated repos since it helps defining responsibility of each module and gives more flexibility for maintainers while reducing the overall size for people consuming only the library. With this in mind I would prefer to move forward with 2 github/npm.

  • Use jest as test runner instead of mocha.

No strong feelings either way, we should consider that a change is always an extra effort that will be time consuming. I think it's safe to have this on the backlog with a lower priority.

  • For code coverage, use istanbul instead of blanket.js. Should keep coveralls? Anything newer and more interesting?

Same thing as above, maybe with a higher priority though since it's probably a less effort-demanding task and Istanbul is the standard for coverage these days.

  • Run node benchmark tests. For this topic, I might grab some ideas from fast-memoize, since I'm not an expert on this subject yet. I'm open for suggestions/help though.

I'll defer to whatever @caiogondim recommends for this one since I have no experience benchmarking libraries.

  • Write code for node.js 6+ and support old versions with Babel transpiler, or move back to fully es5?

Is there any real reason to move back? I think ES6+ is def here to stay and Babel transpilation is popular enough.

from datauri.

heldr avatar heldr commented on July 20, 2024

maxresdefault

@ruyadorno Thanks for the input! Very reasonable thoughts.

One more thing

  • Use Typescript and expose it's .d.ts files right into the repo.

VS.

  • Expose types at @types/datauri

from datauri.

jaulz avatar jaulz commented on July 20, 2024

@heldr I think exposing types as part of this package makes more sense. @types is actually only used if the maintainer does not like them to be in the repository but since you already proposed it i assume you are in favour of it 😊 Let me know if you need help with it or are you already working on it?

from datauri.

heldr avatar heldr commented on July 20, 2024

Closing this since for now I'll be focusing only in TS types.

from datauri.

Related Issues (15)

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.