klaro-js VS dnt

You can use klaro to require consent. To use it, you modify your scripts so they don't load until consent is given for each particular service. Once consent is given for a specific service, klaro updates all scripts belonging to that service (determined by data attributes) so they can be loaded again. This is the only workflow that's completely 'safe' since simply loading the GA script requires consent under GDPR.

I've seen the consent manager recommended: https://github.com/kiprotect/klaro

It’s not really a plug-in. But it works well for usable it’s open source: https://github.com/kiprotect/klaro

You can just follow the link to our website (https://heyklaro.com), we use the CMP there as well.

Having designed several sites and products without frameworks (e.g. https://github.com/kiprotect/klaro/tree/master/src/scss) I think it's way more concise and easy than relying on a framework.

At Taikonauten we build websites for different clients, each with very individual requirements: from corporate websites, online shops and digital service platforms. Trust and credibility towards their clients is a key ingredient for their success, which needs to be reflected in the choice of technology. As such, Klaro’s open-source approach and its highly customizable, versatile set of features made us choose Klaro as our go-to cookie consent tool. Read this article to learn more about how we work with Klaro in our projects.

In order to change the default texts, you need to define the corresponding translation inside your configuration. You can find the translation keys for each language in the official source code.

I have used https://heyklaro.com/ in a couple of projects. Which integrates nicely and comes with a lot of functionality.

Maybe Klaro? https://github.com/kiprotect/klaro

It's FOSS, BSD-3 licensed. It has been in development for three years now, just today I made a new release to improve contextual consent functionality (e.g. for Youtube videos).

We are going to use dnt - Deno to Node Transform tool to build the npm package.

As already mentioned dnt might help you if you are willing to have deno as your primary development environment. I work in a project like this and the deno tooling is great. I don't even need a package.json since dnt will generate it for me.

Build it in Deno and then use dnt to create an npm package. That way you support both JS runtimes: https://github.com/denoland/dnt

Specifically, make my codebase be for Deno, use Deno built-in formatter, linter and testing, and use dnt (Deno to Node Transform) to generate an npm package containing ESM code and to test generated code. For testing in the browser, deploy the test content linked to the generated ESM code to Github Pages and use playwright/test. For Cloudflare Workers, use wrangler to set up a worker locally for testing. A schematic diagram is shown below.

I ended up building the library with Deno and compiling to Node.js CJS and ESM using https://github.com/denoland/dnt

Yes, TS code is compiled to run in browsers. You can compile and bundle using `deno bundle` if your project is developed in Deno. Since I'm using Deno for library development, I use the `dnt`[1] tool to compile them into ESM modules later consumed by esbuild in my Node-based projects/toolchains.

[1] https://github.com/denoland/dnt

Maybe this could help? https://github.com/denoland/dnt