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
{{ message }}
This repository was archived by the owner on Dec 3, 2023. It is now read-only.
This should work, but it does. It should make angular.js recurse but webpack takes care of it.
Many thanks to @huston007 for this even though I didn't merge #17.
Copy file name to clipboardExpand all lines: README.md
+31-3Lines changed: 31 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,19 +5,47 @@ Makes webpack aware of AngularJS modules.
5
5
## Getting Started
6
6
This project is just getting off the ground.
7
7
8
-
It is at the stage now where you can use it to get angular apps webpacked without needing `require()` in your code, but it does it by trying to map between angular module names and file names. The conventions for doing this are various, so it will not fit all cases. Please submit an issue on github if it isn't working for your modules and I'll try to iron out the wrinkles over time.
8
+
It is at the stage now where you can use it to get angular apps webpacked
9
+
without needing `require()` in your code, but it does it by trying to map
10
+
between angular module names and file names. The conventions for doing this are
11
+
various, so it will not fit all cases. Please submit an issue on github if it
12
+
isn't working for your modules and I'll try to iron out the wrinkles over time.
9
13
10
14
To see it in action, I've [forked the angular-seed project](https://github.com/stackfull/angular-seed)
11
15
16
+
## Development
17
+
18
+
Given how complex the problem is, regular test frameworks can't help much. I've
19
+
developed a small grunt task to run compile scenarios and check the output. It's
20
+
less than ideal and a little fragile. To add new scenarios, create a directory
21
+
in test/scenarios containing a webpack.conf.js config file, an `in` and an `out`
22
+
directory. The `in` directory will be used as the source and the output will
23
+
be compared against `out/bundle.js` (ignoring comments etc.).
24
+
25
+
To run the scenarios::
26
+
27
+
grunt webpackScenario
28
+
29
+
by default, it won't show what the output was when it doesn't match, so use
30
+
31
+
grunt --debug webpackScenario
32
+
33
+
In addition, karma tests in the `verify` directory check that the output makes
34
+
a viable executable using the `karma.conf.js` file.
35
+
36
+
The default grunt task checks everything.
12
37
13
38
## Release History
14
39
15
-
#### 0.0.1 - 22 Apr 2014
16
-
First release
40
+
#### 0.0.3 - 7 Dec 2014
41
+
Webpack 1.4 and fix for modules using window.angular
17
42
18
43
#### 0.0.2 - 28 July 2014
19
44
Working well enough to build the angular-seed project.
20
45
46
+
#### 0.0.1 - 22 Apr 2014
47
+
First release
48
+
21
49
22
50
## License
23
51
Copyright (c) 2014 Paul Thomas. Licensed under the MIT license.
0 commit comments