feat: added script to update dist-tags

[mikemimik]

What / Why

While working through our release process, we noticed that there was a lot of updates that needed to be done to the dist-tags each time we release. This previously was a manual process that consumes an amount of time that sometimes required more than one or two otp values.

By scripting this process, it happens quick enough (provided internet connection) that only one otp value needs to be supplied and the script handles all the dist-tag values we'd like to update each release of the cli project.

NOTE: when this pull-request lands we'll update the release process section on updating dist-tags to include the usage of the script.

References

• n/a

[npm-deploy-user]

	angular-quickstart			app-large			app-medium			ember-quickstart			react-app
	prev	current	status	prev	current	status	prev	current	status	prev	current	status	prev	current	status
initial install	41s	34.1s	✅	39.5s	33.8s	✅	34.5s	28.5s	✅	28.1s	22.4s	✅	33.5s	28.8s	✅
repeat install	9.6s	7.1s	✅	8.6s	7.1s	✅	8.3s	6.6s	✅	7.7s	5.9s	✅	9.1s	7s	✅
with warm cache	32.3s	25.5s	✅	33.8s	29.8s	✅	31.3s	24.6s	✅	23.4s	18.4s	✅	29.1s	23.9s	✅
with node_modules	9.2s	7.2s	✅	8.6s	6.3s	✅	9s	8.2s	✅	7.8s	6.3s	✅	9.4s	7.3s	✅
with lockfile	32.6s	23.6s	✅	31s	25.9s	✅	29s	26.1s	✅	21.7s	16.2s	✅	27.4s	21.7s	✅
with warm cache and node_modules	9.3s	7.3s	✅	7.9s	6.2s	✅	8.4s	7.5s	✅	7.6s	6.9s	✅	9.2s	6.9s	✅
with warm cache and lockfile	24.7s	19.5s	✅	26.3s	21.2s	✅	24.3s	17.4s	✅	17.8s	13.9s	✅	21.3s	18.8s	✅
with node_modules and lockfile	10.1s	8.4s	✅	9.8s	7s	✅	8.6s	6.7s	✅	7.8s	6.1s	✅	9.7s	7.4s	✅

[mikemimik]

What / Why

While working through our release process, we noticed that there was a lot of updates that needed to be done to the dist-tags each time we release. This previously was a manual process that consumes an amount of time that sometimes required more than one or two otp values.

By scripting this process, it happens quick enough (provided internet connection) that only one otp value needs to be supplied and the script handles all the dist-tag values we'd like to update each release of the cli project.

NOTE: when this pull-request lands we'll update the release process section on updating dist-tags to include the usage of the script.

References

• n/a

[npm-deploy-user]

	angular-quickstart			app-large			app-medium			ember-quickstart			react-app
	prev	current	status	prev	current	status	prev	current	status	prev	current	status	prev	current	status
initial install	41s	34.1s	✅	39.5s	33.8s	✅	34.5s	28.5s	✅	28.1s	22.4s	✅	33.5s	28.8s	✅
repeat install	9.6s	7.1s	✅	8.6s	7.1s	✅	8.3s	6.6s	✅	7.7s	5.9s	✅	9.1s	7s	✅
with warm cache	32.3s	25.5s	✅	33.8s	29.8s	✅	31.3s	24.6s	✅	23.4s	18.4s	✅	29.1s	23.9s	✅
with node_modules	9.2s	7.2s	✅	8.6s	6.3s	✅	9s	8.2s	✅	7.8s	6.3s	✅	9.4s	7.3s	✅
with lockfile	32.6s	23.6s	✅	31s	25.9s	✅	29s	26.1s	✅	21.7s	16.2s	✅	27.4s	21.7s	✅
with warm cache and node_modules	9.3s	7.3s	✅	7.9s	6.2s	✅	8.4s	7.5s	✅	7.6s	6.9s	✅	9.2s	6.9s	✅
with warm cache and lockfile	24.7s	19.5s	✅	26.3s	21.2s	✅	24.3s	17.4s	✅	17.8s	13.9s	✅	21.3s	18.8s	✅
with node_modules and lockfile	10.1s	8.4s	✅	9.8s	7s	✅	8.6s	6.7s	✅	7.8s	6.1s	✅	9.7s	7.4s	✅

[mikemimik]

What / Why

While working through our release process, we noticed that there was a lot of updates that needed to be done to the dist-tags each time we release. This previously was a manual process that consumes an amount of time that sometimes required more than one or two otp values.

By scripting this process, it happens quick enough (provided internet connection) that only one otp value needs to be supplied and the script handles all the dist-tag values we'd like to update each release of the cli project.

NOTE: when this pull-request lands we'll update the release process section on updating dist-tags to include the usage of the script.

References

• n/a

[npm-deploy-user]

	angular-quickstart			app-large			app-medium			ember-quickstart			react-app
	prev	current	status	prev	current	status	prev	current	status	prev	current	status	prev	current	status
initial install	41s	34.1s	✅	39.5s	33.8s	✅	34.5s	28.5s	✅	28.1s	22.4s	✅	33.5s	28.8s	✅
repeat install	9.6s	7.1s	✅	8.6s	7.1s	✅	8.3s	6.6s	✅	7.7s	5.9s	✅	9.1s	7s	✅
with warm cache	32.3s	25.5s	✅	33.8s	29.8s	✅	31.3s	24.6s	✅	23.4s	18.4s	✅	29.1s	23.9s	✅
with node_modules	9.2s	7.2s	✅	8.6s	6.3s	✅	9s	8.2s	✅	7.8s	6.3s	✅	9.4s	7.3s	✅
with lockfile	32.6s	23.6s	✅	31s	25.9s	✅	29s	26.1s	✅	21.7s	16.2s	✅	27.4s	21.7s	✅
with warm cache and node_modules	9.3s	7.3s	✅	7.9s	6.2s	✅	8.4s	7.5s	✅	7.6s	6.9s	✅	9.2s	6.9s	✅
with warm cache and lockfile	24.7s	19.5s	✅	26.3s	21.2s	✅	24.3s	17.4s	✅	17.8s	13.9s	✅	21.3s	18.8s	✅
with node_modules and lockfile	10.1s	8.4s	✅	9.8s	7s	✅	8.6s	6.7s	✅	7.8s	6.1s	✅	9.7s	7.4s	✅

[mikemimik]

What / Why

While working through our release process, we noticed that there was a lot of updates that needed to be done to the dist-tags each time we release. This previously was a manual process that consumes an amount of time that sometimes required more than one or two otp values.

By scripting this process, it happens quick enough (provided internet connection) that only one otp value needs to be supplied and the script handles all the dist-tag values we'd like to update each release of the cli project.

NOTE: when this pull-request lands we'll update the release process section on updating dist-tags to include the usage of the script.

References

• n/a

[npm-deploy-user]

	angular-quickstart			app-large			app-medium			ember-quickstart			react-app
	prev	current	status	prev	current	status	prev	current	status	prev	current	status	prev	current	status
initial install	41s	34.1s	✅	39.5s	33.8s	✅	34.5s	28.5s	✅	28.1s	22.4s	✅	33.5s	28.8s	✅
repeat install	9.6s	7.1s	✅	8.6s	7.1s	✅	8.3s	6.6s	✅	7.7s	5.9s	✅	9.1s	7s	✅
with warm cache	32.3s	25.5s	✅	33.8s	29.8s	✅	31.3s	24.6s	✅	23.4s	18.4s	✅	29.1s	23.9s	✅
with node_modules	9.2s	7.2s	✅	8.6s	6.3s	✅	9s	8.2s	✅	7.8s	6.3s	✅	9.4s	7.3s	✅
with lockfile	32.6s	23.6s	✅	31s	25.9s	✅	29s	26.1s	✅	21.7s	16.2s	✅	27.4s	21.7s	✅
with warm cache and node_modules	9.3s	7.3s	✅	7.9s	6.2s	✅	8.4s	7.5s	✅	7.6s	6.9s	✅	9.2s	6.9s	✅
with warm cache and lockfile	24.7s	19.5s	✅	26.3s	21.2s	✅	24.3s	17.4s	✅	17.8s	13.9s	✅	21.3s	18.8s	✅
with node_modules and lockfile	10.1s	8.4s	✅	9.8s	7s	✅	8.6s	6.7s	✅	7.8s	6.1s	✅	9.7s	7.4s	✅

[mikemimik]

What / Why

While working through our release process, we noticed that there was a lot of updates that needed to be done to the dist-tags each time we release. This previously was a manual process that consumes an amount of time that sometimes required more than one or two otp values.

By scripting this process, it happens quick enough (provided internet connection) that only one otp value needs to be supplied and the script handles all the dist-tag values we'd like to update each release of the cli project.

NOTE: when this pull-request lands we'll update the release process section on updating dist-tags to include the usage of the script.

References

• n/a

[npm-deploy-user]

	angular-quickstart			app-large			app-medium			ember-quickstart			react-app
	prev	current	status	prev	current	status	prev	current	status	prev	current	status	prev	current	status
initial install	41s	34.1s	✅	39.5s	33.8s	✅	34.5s	28.5s	✅	28.1s	22.4s	✅	33.5s	28.8s	✅
repeat install	9.6s	7.1s	✅	8.6s	7.1s	✅	8.3s	6.6s	✅	7.7s	5.9s	✅	9.1s	7s	✅
with warm cache	32.3s	25.5s	✅	33.8s	29.8s	✅	31.3s	24.6s	✅	23.4s	18.4s	✅	29.1s	23.9s	✅
with node_modules	9.2s	7.2s	✅	8.6s	6.3s	✅	9s	8.2s	✅	7.8s	6.3s	✅	9.4s	7.3s	✅
with lockfile	32.6s	23.6s	✅	31s	25.9s	✅	29s	26.1s	✅	21.7s	16.2s	✅	27.4s	21.7s	✅
with warm cache and node_modules	9.3s	7.3s	✅	7.9s	6.2s	✅	8.4s	7.5s	✅	7.6s	6.9s	✅	9.2s	6.9s	✅
with warm cache and lockfile	24.7s	19.5s	✅	26.3s	21.2s	✅	24.3s	17.4s	✅	17.8s	13.9s	✅	21.3s	18.8s	✅
with node_modules and lockfile	10.1s	8.4s	✅	9.8s	7s	✅	8.6s	6.7s	✅	7.8s	6.1s	✅	9.7s	7.4s	✅

[mikemimik]

What / Why

While working through our release process, we noticed that there was a lot of updates that needed to be done to the dist-tags each time we release. This previously was a manual process that consumes an amount of time that sometimes required more than one or two otp values.

By scripting this process, it happens quick enough (provided internet connection) that only one otp value needs to be supplied and the script handles all the dist-tag values we'd like to update each release of the cli project.

NOTE: when this pull-request lands we'll update the release process section on updating dist-tags to include the usage of the script.

References

• n/a

[npm-deploy-user]

	angular-quickstart			app-large			app-medium			ember-quickstart			react-app
	prev	current	status	prev	current	status	prev	current	status	prev	current	status	prev	current	status
initial install	41s	34.1s	✅	39.5s	33.8s	✅	34.5s	28.5s	✅	28.1s	22.4s	✅	33.5s	28.8s	✅
repeat install	9.6s	7.1s	✅	8.6s	7.1s	✅	8.3s	6.6s	✅	7.7s	5.9s	✅	9.1s	7s	✅
with warm cache	32.3s	25.5s	✅	33.8s	29.8s	✅	31.3s	24.6s	✅	23.4s	18.4s	✅	29.1s	23.9s	✅
with node_modules	9.2s	7.2s	✅	8.6s	6.3s	✅	9s	8.2s	✅	7.8s	6.3s	✅	9.4s	7.3s	✅
with lockfile	32.6s	23.6s	✅	31s	25.9s	✅	29s	26.1s	✅	21.7s	16.2s	✅	27.4s	21.7s	✅
with warm cache and node_modules	9.3s	7.3s	✅	7.9s	6.2s	✅	8.4s	7.5s	✅	7.6s	6.9s	✅	9.2s	6.9s	✅
with warm cache and lockfile	24.7s	19.5s	✅	26.3s	21.2s	✅	24.3s	17.4s	✅	17.8s	13.9s	✅	21.3s	18.8s	✅
with node_modules and lockfile	10.1s	8.4s	✅	9.8s	7s	✅	8.6s	6.7s	✅	7.8s	6.1s	✅	9.7s	7.4s	✅

[mikemimik]

What / Why

While working through our release process, we noticed that there was a lot of updates that needed to be done to the dist-tags each time we release. This previously was a manual process that consumes an amount of time that sometimes required more than one or two otp values.

By scripting this process, it happens quick enough (provided internet connection) that only one otp value needs to be supplied and the script handles all the dist-tag values we'd like to update each release of the cli project.

NOTE: when this pull-request lands we'll update the release process section on updating dist-tags to include the usage of the script.

References

• n/a

[npm-deploy-user]

	angular-quickstart			app-large			app-medium			ember-quickstart			react-app
	prev	current	status	prev	current	status	prev	current	status	prev	current	status	prev	current	status
initial install	41s	34.1s	✅	39.5s	33.8s	✅	34.5s	28.5s	✅	28.1s	22.4s	✅	33.5s	28.8s	✅
repeat install	9.6s	7.1s	✅	8.6s	7.1s	✅	8.3s	6.6s	✅	7.7s	5.9s	✅	9.1s	7s	✅
with warm cache	32.3s	25.5s	✅	33.8s	29.8s	✅	31.3s	24.6s	✅	23.4s	18.4s	✅	29.1s	23.9s	✅
with node_modules	9.2s	7.2s	✅	8.6s	6.3s	✅	9s	8.2s	✅	7.8s	6.3s	✅	9.4s	7.3s	✅
with lockfile	32.6s	23.6s	✅	31s	25.9s	✅	29s	26.1s	✅	21.7s	16.2s	✅	27.4s	21.7s	✅
with warm cache and node_modules	9.3s	7.3s	✅	7.9s	6.2s	✅	8.4s	7.5s	✅	7.6s	6.9s	✅	9.2s	6.9s	✅
with warm cache and lockfile	24.7s	19.5s	✅	26.3s	21.2s	✅	24.3s	17.4s	✅	17.8s	13.9s	✅	21.3s	18.8s	✅
with node_modules and lockfile	10.1s	8.4s	✅	9.8s	7s	✅	8.6s	6.7s	✅	7.8s	6.1s	✅	9.7s	7.4s	✅

[mikemimik]

What / Why

While working through our release process, we noticed that there was a lot of updates that needed to be done to the dist-tags each time we release. This previously was a manual process that consumes an amount of time that sometimes required more than one or two otp values.

By scripting this process, it happens quick enough (provided internet connection) that only one otp value needs to be supplied and the script handles all the dist-tag values we'd like to update each release of the cli project.

NOTE: when this pull-request lands we'll update the release process section on updating dist-tags to include the usage of the script.

References

• n/a

[npm-deploy-user]

	angular-quickstart			app-large			app-medium			ember-quickstart			react-app
	prev	current	status	prev	current	status	prev	current	status	prev	current	status	prev	current	status
initial install	41s	34.1s	✅	39.5s	33.8s	✅	34.5s	28.5s	✅	28.1s	22.4s	✅	33.5s	28.8s	✅
repeat install	9.6s	7.1s	✅	8.6s	7.1s	✅	8.3s	6.6s	✅	7.7s	5.9s	✅	9.1s	7s	✅
with warm cache	32.3s	25.5s	✅	33.8s	29.8s	✅	31.3s	24.6s	✅	23.4s	18.4s	✅	29.1s	23.9s	✅
with node_modules	9.2s	7.2s	✅	8.6s	6.3s	✅	9s	8.2s	✅	7.8s	6.3s	✅	9.4s	7.3s	✅
with lockfile	32.6s	23.6s	✅	31s	25.9s	✅	29s	26.1s	✅	21.7s	16.2s	✅	27.4s	21.7s	✅
with warm cache and node_modules	9.3s	7.3s	✅	7.9s	6.2s	✅	8.4s	7.5s	✅	7.6s	6.9s	✅	9.2s	6.9s	✅
with warm cache and lockfile	24.7s	19.5s	✅	26.3s	21.2s	✅	24.3s	17.4s	✅	17.8s	13.9s	✅	21.3s	18.8s	✅
with node_modules and lockfile	10.1s	8.4s	✅	9.8s	7s	✅	8.6s	6.7s	✅	7.8s	6.1s	✅	9.7s	7.4s	✅