Skip to content

Wrong result of import after updating modules to 0.9.0 #33

Closed
@SimonSimCity

Description

@SimonSimCity

I guess your extension here is incompatible with modules since v0.9.0. It's quite easy to reproduce. Here's a quick manual of how to do it. Install a plugin (like hwillson:stub-collections) into a fresh project (like described here: hwillson/meteor-stub-collections#17 (comment)). Run the project by calling meteor and you see, that it works as expected. In your console you see that the import returns

I20170628-11:34:13.452(4)? { add: [Function], stub: [Function], restore: [Function] }

It also returns this result after replacing ecmascript by your plugin while modules is on v0.8.2 or lower. But after updating this module the result changes into:

I20170628-11:36:28.382(4)? { default: { add: [Function], stub: [Function], restore: [Function] } }

If I now replace your plugin back with ecmascript while leaving modules in a version like v0.9.0 I get the expected first result again.

I suppose, this has something to do with your plugin being incompatible with the latest changes of the modules package ... or am I mistaken here?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions