Skip to content

Closure Library deprecation #1175

Open
Open
@emaxx-google

Description

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

Activity

emaxx-google

emaxx-google commented on Jun 12, 2024

@emaxx-google
CollaboratorAuthor

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

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

      Participants

      @emaxx-google

      Issue actions

        Closure Library deprecation · Issue #1175 · GoogleChromeLabs/chromeos_smart_card_connector