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

Closure Library deprecation #1175

Open
emaxx-google opened this issue Jun 12, 2024 · 1 comment
Open

Closure Library deprecation #1175

emaxx-google opened this issue Jun 12, 2024 · 1 comment

Comments

@emaxx-google
Copy link
Collaborator

Our codebase here relies a lot on Closure Library, which got deprecated and is about to be sunset: google/closure-library#1214

@emaxx-google
Copy link
Collaborator Author

In the short term, we don't need to do anything as we pin the Closure Library to a version that we import and store under //third_party/closure-library/. So as long as there's no serious issue discovered (which we cannot fix in our copy) or incompatibility with future browser versions, we can in theory sit indefinitely on top of it.

For the long-term perspective, if we were to start migrating off it, the whole list of functionality used by us is pretty long, but what we rely most heavily upon is:

  • logging,
  • message channels,
  • Disposable,
  • the unit test and mock framework.

It seems that there's no ready-to-use list of replacement libraries for specific features, so the work would require analyzing these dependencies and finding analogs or reimplementing. As it was pointed out to me, this work might also require switching to more modern technologies like TypeScript, NPM, esbuild, etc.

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

No branches or pull requests

1 participant