Skip to content

Conversation

tomratcliffe
Copy link

This is needed when migrating angular.js to use webpack, and the existing unit tests call module('myModule'). This causes problems as module is a reserved/special word for webpack use, and the unit tests won't compile (complaining that module is not a function). The solution is to use angular.mock.module('myModule'). This rule change adds a webpack-support option (open to renaming this), and adds a fixer that can sort out the problems found (to save on Ctrl+F'ing through the code and finding issues).

Please see the following for more context/examples:
https://stackoverflow.com/questions/32499108/karma-jasmine-webpack-module-is-not-a-function
https://stackoverflow.com/questions/39360164/module-is-not-a-function-karma-jasmine-webpack-angular?rq=1

This is needed when migrating angular.js to use webpack, and the existing unit tests call `module('myModule')`. This causes problems as `module` is a reserved/special word for webpack use, and the unit tests won't compile. The solution is to use `angular.mock.module('myModule')`. This rule change adds a `webpack-support` option (open to renaming this), and adds a fixer that can sort out the problems found (to save on Ctrl+F'ing through the code and finding issues).
@tomratcliffe
Copy link
Author

Hi @EmmanuelDemey, have you had a chance to look at this yet? Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant