#50052 We should freeze all npm packages versions
Closed: fixed 2 months ago by spichugi. Opened 11 months ago by spichugi.

Issue Description

All software changes incur some risk, and it's critical to be able to manage this risk.
We can use a common way of dealing with it - npm-shrinkwrap.

NAME
       npm-shrinkwrap -- Lock down dependency versions

SYNOPSIS
       npm shrinkwrap

DESCRIPTION
       This  command  locks down the versions of a package's dependencies so
       that you can control exactly which versions of each  dependency  will
       be used when your package is installed.

Metadata Update from @mreynolds:
- Custom field component adjusted to None
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None
- Issue set to the milestone: 1.4.1

10 months ago

Metadata Update from @spichugi:
- Issue assigned to spichugi

5 months ago

Metadata Update from @spichugi:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

2 months ago

Login to comment on this ticket.

Metadata