-
Notifications
You must be signed in to change notification settings - Fork 61
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
Switching from 3.0.4 to 4.0.0 results in TypeError: Cannot read property 'replace' of undefined while parsing file #66
Comments
Hey! I am looking into it for you. Out of curiosity does something like this |
Is this what you mean?
|
For completeness, it succeeds on 3.0.4:
|
No, not quite. I wanted to see if passing an option to But let me try to just replicate it just as you have it in the latter two examples and see where I get on. |
Okay, cool, I was able to replicate and it's having issues on |
I'm seeing the same issue but with |
the TypeError is masking the real error the return value from The underlying error (at least those I have had) alwasy relate to invalid options (for uglify) - this is because the I think this modules should do suitable checking of the return value of |
I hacked the following PR, which tackles the swallowed |
Ok, so uglify no longer supports shortened CLI in there JS api, but hopefully that is fixed for you in 📦 I still want to address creating a new opts object, and that should be fixed by @iamjochem #69. |
I don't have a minimal reproduction yet, but using
|
Sounds like the browserify option `._flags` isn't being deleted when it
should be
…On Wed, Jun 28, 2017 at 9:28 PM Tristan Slominski ***@***.***> wrote:
I don't have a minimal reproduction yet, but my production use case
results in:
`_flags` is not a supported option
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#66 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACWleqg3ZwkjU7cpAiZYon1xkOQrQZ2Pks5sIqlvgaJpZM4N6JfK>
.
|
I'm also affected by |
Actual command I use:
It succeeds with uglifyify version 3.0.4 and fails with version 4.0.0 as follows:
Furthermore, removing
uglifyify
from the toolchain also succeeds, so that the dependencies listed above succeed using this command:The text was updated successfully, but these errors were encountered: