You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
On Sat, Aug 12, 2023 at 12:10 AM Zavier Miller ***@***.***> wrote:
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?
—
Reply to this email directly, view it on GitHub
<#2>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAHDJYP2MYUHF4LQZ23RD3XU4F5JANCNFSM6AAAAAA3NWNKAM>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
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 entirereceipt-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?
The text was updated successfully, but these errors were encountered: