-
Notifications
You must be signed in to change notification settings - Fork 298
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When.js failing test #92
Conversation
One suggested fix for the above would be to "statically detect" these AMD-style wrappers, and "unwrap" them in a loader before passing back to Webpack for analysis. |
I was just about to create a |
I've added the fix for this case, based on a very specific wrapper detection. While the code is highly overly-specific, I think there will be ways to generalize the approach to better analysis methods as it expands, but i think as a starting point starting specific then moving to more general analysis makes sense, driven by the test cases. |
02b0b3b
to
ad4ced0
Compare
Codecov Report
@@ Coverage Diff @@
## master #92 +/- ##
==========================================
+ Coverage 69.78% 70.84% +1.05%
==========================================
Files 3 3
Lines 331 343 +12
==========================================
+ Hits 231 243 +12
Misses 100 100
Continue to review full report at Codecov.
|
@guybedford can you:
|
ad4ced0
to
40b6eaa
Compare
Posted #95 which would replace a lot of the logic with a partial evaluator. |
40b6eaa
to
b980f7a
Compare
When defines itself using the wrapper pattern:
Similarly to #87 we have the static analysis problem of not knowing that the internal requires are external requires... (although in theory this static analysis is a trivial compiler problem :P).
This seems to be the bug behind "jugglingdb" builds as far as I can tell.