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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add copyright banner to UMD variant #429

Closed

Conversation

codeworrior
Copy link

When adding this library to our project (not on github, so I can't share a link, sorry), we noticed that the minified UMD variant (dist/index.min.js) only contains a copyright comment for the external ts-custom-error module, but none for your own modules. This looked a bit misleading to us.

This PR is a proposal how to address this. It uses a rollup plugin to add your LICENSE file as a banner comment to the build result. The banner is added in a way that terser doesn't remove it (/*! ... */ comment).

@werthdavid werthdavid closed this Apr 26, 2022
@codeworrior
Copy link
Author

Has this been solved in a different way?

@werthdavid
Copy link
Member

That was a mistake, sorry. I'll look into the changes you made

@werthdavid werthdavid reopened this Apr 26, 2022
},
data() {
return {
foo: 'foo',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what does that mean?

@@ -504,7 +504,7 @@ arr-union@^3.1.0:
resolved "https://registry.yarnpkg.com/arr-union/-/arr-union-3.1.0.tgz#e39b09aea9def866a8f206e288af63919bae39c4"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess a fresh install to update that file would be useful

@codeworrior
Copy link
Author

Thanks! It's not a big thing. Just thought, the copyright comments in the UMD version should match the reality...

@werthdavid
Copy link
Member

Have you seen my comments in the code?

@codeworrior
Copy link
Author

Yes, sorry for not replying immediately - daily work, you know. I hope to be able to look into this again today or tomorrow.

Kind Regards and thanks again,
Frank

@werthdavid
Copy link
Member

any updates?

Copy link

Stale pull request message

@codeworrior
Copy link
Author

Sorry that I didn't manage to update the PR. Fair enough to close it after such a long time.

@werthdavid
Copy link
Member

if you manage to update it we can reopen it!

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

Successfully merging this pull request may close these issues.

2 participants