Change Details

We currently have a mix of scoped and unscoped packages associated with the wikimedia org in npm. We should standardize on scoping or not scoping them to the wikimedia org, and make adjustments as needed. The trend is for packages to be scoped, but doing so has both pros and cons. Pros: - Helps prevent naming collisions Cons: - Causes trouble for Windows users due to directory name length?

We currently have a mix of scoped and unscoped packages associated with the wikimedia org in npm. We should standardize on scoping or not scoping them to the wikimedia org, and make adjustments as needed. The trend is for packages to be scoped, but doing so has both pros and cons. Pros: - Helps prevent naming collisions - Helps establish provenance of the code Cons: - Causes trouble for Windows users due to directory name length?

We currently have a mix of scoped and unscoped packages associated with the wikimedia org in npm. We should standardize on scoping or not scoping them to the wikimedia org, and make adjustments as needed. The trend is for packages to be scoped, but doing so has both pros and cons. Pros: - Helps prevent naming collisions - Helps establish provenance of the code Cons: - Causes trouble for Windows users due to directory name length?