ReferenceError: module is not defined

[countcain]

I have a legacy meteor 1.2.1 project. After I upgrade my meteor cli to 1.3, problems occurred!!

I don't know how to debug this. Cannot track exactly which file is related to this module is not defined error.

Btw
I really regret using meteor. I spent about 70% of my dev time to figure out how to fix various bugs of meteor, issues occurred in deploying, developing, plugins installing, odd performance. Only 30% of my time is real work. Really sad. I am rewriting the whole project using other low coupling libraries .

[countcain]

As for this bug, I wonder is there any way to know the exactly code block that cause the error

[benjamn]

Um, your screenshot cut off the most useful information… but my guess is that you need to run meteor add ecmascript which implies the modules package, which is what provides the module variable. The ecmascript package has been installed by default for all new apps since 1.2, so I'm somewhat surprised you were not already using it.

Once you add the ecmascript package, you can put your ES2015 code in .js files rather than .es6 files, and at some point you should be able to stop using whatever compiler plugin is compiling those .es6 files (once you've converted everything to .js files).

[abernix]

I'm going to close this because we haven't heard anything back from you about this problem and it seems to be an isolated situation or strangeness in your setup. Would be happy to reopen it if you come up with some additional details that are helpful in resolving it! :)