Skip to content

Dependency Updates #4

@jasondashwang

Description

@jasondashwang

I would update some packages due to some security vulnerabilities such as morgan and migrate off npm's package-lock.json to yarn because of a deterministic package dependency tree and just objectively better caching algorithm for dev needs.

The yarn migration is quite simple:
https://yarnpkg.com/lang/en/docs/migrating-from-npm/

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions