Skip to content

[Infrastructure] Figure out a process to reliably update our JS tooling and dependencies on a regular cadence #29925

Closed
@javiercn

Description

@javiercn

We currently don't have a process in place to update our JS dependencies in the same way we update other dependencies. This makes these dependencies go stale and makes it harder to update later on, as well as prevents us from reaping benefits that new versions normally bring.

We want to have a process for updating things like Webpack and Typescript on a regular basis so that we can leverage new features and target more modern JavaScript.

It would be ideal if we can centralize the versions of these things in one place as well as if we upgrade other dependencies like yarn (currently using 1.13, 2.0 has been out for a while).

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-infrastructureIncludes: MSBuild projects/targets, build scripts, CI, Installers and shared frameworktask

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions