requirejs still a dev dependency in some package.json files

[zepumph]

I think that universally these shouldn't be needed, but I thought I would check with everyone before deleting.

chipper
installer-builder
phet-io
phet-io-wrappers
studio

Found in the above repos' package.json file.

[chrisklus]

From 4/2/20 dev meeting:

Related to #905.
We're happy with this being deleted. Thanks!

@zepumph please assign @Denz1994 to verify that the installer-builder is all good when you're finished.

[pixelzoom]

3 repos (chipper, phet-io-wrappers, studio) have this in package.json. I have no idea whether this is vestigial, is still a dependency, or is a dependency that needs to be removed.

"requirejs": "~2.3.3"

All repos have something like this in package.json. If the namespace is still needed, it should probably be renamed to something other than "requirejsNamespace".

"requirejsNamespace": "ACID_BASE_SOLUTIONS",

[ariel-phet]

@jonathanolson said he can handle this issue (consult with @chrisklus if you have iO related questions).

[ariel-phet]

Marking as high priority as we would like to clean up ES-6 modules issues in a timely manner

[jonathanolson]

Verified it was OK to remove, and removed in the above commits.

All repos have something like this in package.json. If the namespace is still needed, it should probably be renamed to something other than "requirejsNamespace"

That's the best name we have for it, since it's specifically to work with how we USED to handle string keys. Should that be tagged for dev meeting discussion? I recall others feeling that it wasn't the best name also.

[pixelzoom]

Verified that "requirejs": "~2.3.3" entries were removed.

It doesn't look like "requirejsNamespace" was addressed, see #920 (comment). Back to @jonathanolson.

[jonathanolson]

It doesn't look like "requirejsNamespace" was addressed

Correct, I mentioned:

That's the best name we have for it, since it's specifically to work with how we USED to handle string keys. Should that be tagged for dev meeting discussion? I recall others feeling that it wasn't the best name also.

Proactively tagging this for developer meeting, so we can discuss.

[pixelzoom]

Sorry, I somehow missed that. I'm OK with leaving it as "requirejsNamespace".