Add support for TCFv2 and modernize the web extension

[charles-tan]

• Call TCFv2 APIs
• Refactor of backend
• Modernize the UI and expose more info returned in the TC string

[Perdu]

Hello,
Thanks for submitting a pull request and for the extensive work to support TCFv2.
Apologies for the delay. I have some time new to work on integrating this and pushing it to firefox and chrome stores.
However, I have a few blocking issues:

• the first one is that the provided build command currently fails on my setup:

$ yarn run build
yarn run v1.22.19
$ node utils/build.js
[PATH]/Cookie-Glasses/utils/build.js:8
  (err) => { if (err) throw err; },
                      ^

ValidationError: Invalid configuration object. Webpack has been initialized using a configuration object that does not match the API schema.
[...]

• Are the dependencies to yarn and webpack necessary?
• There are a lot of dependencies in package.json. Can you justify all of them? I can't seem to find use for some of them (e.g. "acorn") in the code.
• Can you explain why there is a web server in utils/?

The rest is minor and I can fix it later.

Thanks!

[charles-tan]

Hello, Thanks for submitting a pull request and for the extensive work to support TCFv2. Apologies for the delay. I have some time new to work on integrating this and pushing it to firefox and chrome stores. However, I have a few blocking issues:

• the first one is that the provided build command currently fails on my setup:

$ yarn run build
yarn run v1.22.19
$ node utils/build.js
[PATH]/Cookie-Glasses/utils/build.js:8
  (err) => { if (err) throw err; },
                      ^

ValidationError: Invalid configuration object. Webpack has been initialized using a configuration object that does not match the API schema.
[...]

• Are the dependencies to yarn and webpack necessary?
• There are a lot of dependencies in package.json. Can you justify all of them? I can't seem to find use for some of them (e.g. "acorn") in the code.
• Can you explain why there is a web server in utils/?

The rest is minor and I can fix it later.

Thanks!

Hi, it's been quite some time since I looked at this and I've lost some context. I'll try to revisit this and look into cleaning up some dependencies. We finished this project in a bit of a hurry and I'm sure there are unused dependencies that we might have explored using and never cleaned up.

I was able to rebuild from a fresh setup. I'm using yarn version 1.22.19, npm version 9.2.0, node version v18.8.0. What versions are you using and can you provide some error logs from when you tried running yarn run build?

I recall that we used yarn because we found it easier for our dependency management, we were running into some issues with plain npm. Beyond that, I can't remember unfortunately. Is yarn something you're trying to avoid?

[charles-tan]

Webpack is not strictly necessary, but we found it to be useful for development. The webserver in utils/ is part of common chrome extension boilerplate using webpack (see https://github.com/samuelsimoes/chrome-extension-webpack-boilerplate and https://www.npmjs.com/package/chrome-extension-boilerplate-react). We try to stick to the design that the boilerplate code sets us up with. We found the interaction between scripts made more sense when we made this switch.

I apologize for the messy commit history... I tracked down the old PR where this change was implemented. There is some good context there behind our rationale for using yarn + webpack.

[Perdu]

Hello,

I have the following versions:

• yarn 1.22.19
• npm 8.19.2 (for some reason arch is a bit behind for this package)
• node 19.4.0 (this also failed with node 16.19.0)

I'll come back to this a bit later, but I may remove webpack, especially since most dependencies are gone.

Don't worry about the commit history, I'll probably squish everything into a single commit when merging

[Perdu]

So, some updates as I've spent some time trying to integrate this:

• I've tried fixing the webpack crashes (see the webpack branch) to be able to build this, but with webpack pulling over 500 dependency modules (!), I don't expect this to be maintainable
• I've tried removing webpack altogether (see the tcfv2integration branch), but this seems too dependent on it as it's pulling @iabtcf/core as a dependency, and I don't know how to integrate this without extensive work

Honestly, I don't think I'll spend more time working on this as this project is no longer important to me.