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
The MIT license is very liberal (thank you), but I also wanted to check your own preferences as developer/maintainer:
Are you comfortable with PapaParse being bundled as a separate file in the distro of another JavaScript library?
Are you comfortable with PapaParse being combined with another JavaScript library in an all-in-one min-ified file (assuming full credit and a pointer to the original and its license info in the docs)?
Thanks. My particular use case is a Public Domain library for processing humanitarian-crisis data at the UN (and elsewhere), but this question is probably of broader interest.
The text was updated successfully, but these errors were encountered:
Yep, that's totally fine. Just take the license along with it (meaning, include the license file in there somewhere). It would be good to update your copy of the library occasionally to get the latest bug fixes.
Yeah that's good too. Just be aware that if you do this, you can't use the worker thread feature unless the other libs in the same file are hardened for worker environments, which is unlikely.
Thanks for asking! And always happy to see Papa being used for something so good.
The MIT license is very liberal (thank you), but I also wanted to check your own preferences as developer/maintainer:
Thanks. My particular use case is a Public Domain library for processing humanitarian-crisis data at the UN (and elsewhere), but this question is probably of broader interest.
The text was updated successfully, but these errors were encountered: