Skip to content

Figure out best way to split up packages #2

@zaviermiller

Description

@zaviermiller

Right now, each independent part of this project is its own package.

I originally felt this was best since that would allow for plugin developers to only install the package(s) they need; however, now I am thinking that the hassle may not be worth it.

Do we really need 5 different packages to make this thing work?

One potential solution would be to create a separate types package that would allow devs to pull in only types if that's all they needed.

With this, though, I go back to thinking about the receipt-escpos-renderer package. There are some useful utils in there that people building their own nodes could use. Would they want to import the entire receipt-components package? I'm not sure.

None of this may even matter. The end-user will have all packages installed so does it really matter if a developer has to install slightly more on their own machine?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions