Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inquiry regarding re-exposure of chroma.js #327

Open
EDM115 opened this issue Feb 11, 2024 · 0 comments
Open

Inquiry regarding re-exposure of chroma.js #327

EDM115 opened this issue Feb 11, 2024 · 0 comments

Comments

@EDM115
Copy link

EDM115 commented Feb 11, 2024

Hello 馃憢

I'm currently working on a color palette generator package, and it uses chroma.js
I am considering re-exposing the chroma object as part of my package's public API. This would involve importing chroma.js and exporting it directly to users of my package, alongside my own functions, like this :

import chroma from 'chroma-js'

// functions...

export {
    chroma,
    // functions...
}

Before proceeding with this approach, I wanted to reach out and ensure that this use case aligns with your licensing terms and your vision for chroma.js's application in external projects. My goal is to respect your work and comply with any guidelines you may have for using chroma.js in this manner.
Also, do I need to add your license alongside mine (my project will be released under the MIT License) ?

Thanks in advance

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant