Ensure @ember/application/deprecations is stripped in addition to @ember/debug.

[bekzod]

emberjs/ember.js#17926 (comment)

[bekzod]

thank you @rwjblue, accepted all those changes

[rwjblue]

@bekzod - I've pushed a few changes:

• added a failing test that attempts to confirm the babel-plugin-ember-modules-api-polyfill doesn't transpile import { deprecate } from '@ember/application/deprecations' to globals (e.g. Ember.deprecate)
• fix that failing test (by ensuring that deprecate from @ember/application/deprecations is not transformed by the modules polyfill
• added a test confirming that import { deprecate } from '@ember/application/deprecations is transpiled properly in debug builds

Should be good to land once CI is finished...

[stefanpenner]

running the same plugin twice seems unfortunate, can the primary plugin simply be taught how to handle this case?

[rwjblue]

We already support arbitrary module paths with flags, but not with debugTools. We can definitely update babel-plugin-debug-macros to support that though.

[stefanpenner]

i think this may be tripping up https://github.com/babel/babel/blob/11fa2461cec930168fd43cfeda733aab056d8318/packages/babel-core/src/config/config-descriptors.js#L240

[stefanpenner]

investigating

[stefanpenner]

The issue seems to have been a monorepo with a shared lockfile resulted in an incomplete semver drift of relevant dependencies, upgrading all repos contained within the monorepo fixed the issues.