Closed brianmhunt closed 2 years ago
^^ This has ~100 weekly downloads and is a top-level match so we may want to repurpose as e.g. @tko/build.reference
npm deprecate --otp $OTP tko.utils "Replaced by packages from the @tko organization"
npm deprecate --otp $OTP tko.binding.core "Replaced by packages from the @tko organization"
npm deprecate --otp $OTP tko.computed "Replaced by packages from the @tko organization"
npm deprecate --otp $OTP tko.utils.jsx "Replaced by packages from the @tko organization"
npm deprecate --otp $OTP tko.observable "Replaced by packages from the @tko organization"
npm deprecate --otp $OTP tko.bind "Replaced by packages from the @tko organization"
npm deprecate --otp $OTP tko-policy "Replaced by packages from the @tko organization"
npm deprecate --otp $OTP tko.binding.template "Replaced by packages from the @tko organization"
npm deprecate --otp $OTP tko.filter.punches "Replaced by packages from the @tko organization"
npm deprecate --otp $OTP tko.binding.if "Replaced by packages from the @tko organization"
npm deprecate --otp $OTP tko.provider "Replaced by packages from the @tko organization"
npm deprecate --otp $OTP tko.provider.mustache "Replaced by packages from the @tko organization"
$ OTP=xxxxxx bash x.sh
Background
A number of the
@tko
andtko.*
packages have been created and deployed to npm along the way, mostly dating to the early experiments with packaging. These no longer needed, and may confuse potential consumers of the packages.The
@tko/*
packages will continue; this is just for any older and unused packages (notably, likelytko.*
).Objective
Technical design
O1: Compile a list
This should be possible with a simple search of npmjs.org (or otherwise).
O2: Mark the packages as deprecated
npm
provides a handydeprecate
command that should serve properly advise users that the package is not used.