Use require
instead of import
to make Embroider happy
#20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Switches to the
require
global to access what was previouslyimport
ed. Since Embroider won't expose synthetic modules, only real ones that Node module resolution would be able access. As mentioned inside the comment, it's a recommended way of doing such things by the Ember Core team members.Also adds
focus-trap
todevDependencies
to work around this issue. (focus-trap
is a dependency ofember-bootstrap
which is being used for the dummy app).The Embroider scenarios are all based on versions of Ember & Ember Data currently defined in
package.json
, which are3.28
at the moment.Special thanks to @mansona <3