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

feat: don't require ua-parser-js in lambda-context #170

Merged
merged 1 commit into from
Nov 21, 2024
Merged

Conversation

birtles
Copy link
Member

@birtles birtles commented Nov 21, 2024

BREAKING CHANGE: If you want to continue to use ua-parser-js in
lambda-context you will need to use lambdaContextWithUaParser and
pass in your own parser function as described here:
https://github.com/birchill/bugsnag-zero?tab=readme-ov-file#using-a-custom-user-agent-string-parser

This is because from version ua-parser-js version 2 onwards, users are
required to either use the AGPL version or license the library.

It's best to allow users of this package to decide how they want to
consume ua-parser-js.

BREAKING CHANGE: If you want to continue to use `ua-parser-js` in
`lambda-context` you will need to use `lambdaContextWithUaParser` and
pass in your own parser function as described here:
https://github.com/birchill/bugsnag-zero?tab=readme-ov-file#using-a-custom-user-agent-string-parser

This is because from version `ua-parser-js` version 2 onwards, users are
required to either use the AGPL version or license the library.

It's best to allow users of this package to decide how they want to
consume `ua-parser-js`.
@birtles birtles merged commit 3ab253c into main Nov 21, 2024
1 check passed
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

Successfully merging this pull request may close these issues.

1 participant