License responsibilities for web usage is unclear.

[Splizard]

The original project was MIT, this refactored version is LGPLv3/later. This change makes the project more difficult to use.

Let me walk you through my use-case and what I'm unclear about, I would like to provide developers generated typescript bindings or header code for an HTTP API that returns JSON objects that can contain 64 bit integer values.

I would like to use this project to handle the serialization layer for the communication with these APIs. Although it's clear that I can distribute copies of json-bigint (and the license) along with the bindings to any developers who will subsequently have the freedom to modify json-bigint. When these developers build their typescript projects for the browser, how do they make sure that their users are aware of and can modify and relink json-bigint?

Is it enough to add a script tag with a license note that a user can edit using the inspector in their web browser? Documentation on the expected responsibilities for this scenario would be very helpful.