You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I first noticed this when I was messing with: NullVoxPopuli/ember-statechart-component#244 (which relies on an initializer to utilize setComponentManager) -- it presented itself via ember saying that it didn't know of a component manager to handle StateNode (from xstate) -- which now makes sense, because the initializer code is in a chunk that runs after initializers are needed.
Odd things that can be noticed:
the module can be imported twice (a log is at module-level in the initializer, and logs when the app/test boots, and again during import)
the initializer only runs once (when called manually in the test) -- I'd expect the initializer to run during app/test boot?
The text was updated successfully, but these errors were encountered:
The reason your initializer isn't running normally is that your test isn't using one of the setup functions from ember-qunit. You need at least import { setupTest } from 'ember-qunit'.
The reason your module is getting duplicated is that your app imports the initializer from the path
I confirmed that by adding setupTestand by changing my import to have .js at the end, the test in the example passes.
Which I should have included in the OP, but (for completeness) it's:
Reproduction: https://github.com/NullVoxPopuli/ember-addon-v2-duplicate-modules
I first noticed this when I was messing with: NullVoxPopuli/ember-statechart-component#244 (which relies on an initializer to utilize
setComponentManager
) -- it presented itself via ember saying that it didn't know of a component manager to handleStateNode
(from xstate) -- which now makes sense, because the initializer code is in a chunk that runs after initializers are needed.Odd things that can be noticed:
The text was updated successfully, but these errors were encountered: