[webcomponents.org] Unable to process element {"message": "Registry metadata is too big", "code": 16}

[t2ym]

[webcomponents.org] Unable to process element {"message": "Registry metadata is too big", "code": 16}

Error Messages have changed

Error - 16
Unable to process element
{"message": "Registry metadata is too big", "code": 16}

https://www.webcomponents.org/element/i18n-element

Root Cause

• The size of registry metadata at https://registry.npmjs.org/i18n-element exceeds 1000000 (~1M) bytes in expanded format. The size is actually 1.4MB.
• The limit size is set with the change https://github.com/webcomponents/webcomponents.org/commit/62a751ef3f6bd432e673ce12200a742c5c653212 with the PR https://github.com/webcomponents/webcomponents.org/pull/1241
  • The original size limit by Google App Engine: https://web.archive.org/web/20120101050516/http://code.google.com/intl/en/appengine/docs/python/datastore/overview.html#Quotas_and_Limits

Limit	Amount
maximum entity size	1 megabyte
maximum number of values in all indexes for an entity (1)	5,000 values

Status

• Investigating how to minimize the registry metadata
• Quoted from npm unpublish documentation

With the default registry (registry.npmjs.org), unpublish is only allowed with versions published in the last 72 hours. If you are trying to unpublish a version published longer ago than that, contact support@npmjs.com.

• Is it acceptable to unpublish older versions with the help of support@npmjs.com?

Notes

• Feedback has been sent to the site with the issue https://github.com/webcomponents/webcomponents.org/issues/1239

Workarounds

• Show bower documents