npm versions limit (#17030)

* Add note about this

* Apply suggestions from code review

* Apply suggestions from code review

Co-authored-by: Bryan Clark <clarkbw@github.com>

* Apply suggestions from code review

Co-authored-by: Bryan Clark <clarkbw@github.com>

Author: jmarlena

content/packages/guides/configuring-npm-for-use-with-github-packages.md

@@ -16,6 +16,17 @@ versions:
 
 {% data reusables.package_registry.admins-can-configure-package-types %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
+### Limits for published npm versions
+
+If you publish over 1,000 npm package versions to {% data variables.product.prodname_registry %}, you may see performance issues and timeouts occur during usage.
+
+To reduce the number of versions you have published for your npm package, consider deleting package versions. For more information, see "[Deleting a package](/packages/manage-packages/deleting-a-package)."
+
+In the future,  {% data variables.product.company_short %} will enforce a hard limit on publishing more than 1,000 versions of an npm package.  When we start enforcing the 1,000 versions limit for each npm package hosted on {% data variables.product.prodname_registry %}, we will offer more guidance on how to manage your package versions.
+
+{% endif %}
+
 ### Authenticating to {% data variables.product.prodname_registry %}
 
 {% data reusables.package_registry.authenticate-packages %}