Skip to content
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

fix parsing of property access after new line #1944

Merged
merged 1 commit into from May 15, 2017

Conversation

alexlamsl
Copy link
Collaborator

@alexlamsl alexlamsl commented May 15, 2017

Account for comments when detecting property access in tokenizer.

fixes #1943

@kzc
Copy link
Contributor

kzc commented May 15, 2017

@alexlamsl So now we know what the original parse code was for. :-)

@alexlamsl
Copy link
Collaborator Author

So now we know what the original parse code was for. :-)

Heh. Except I think that is a workaround for the deficancies of tokenizer, so I just push a new fix which I think actually resolves this issue properly.

Account for comments when detecting property access in `tokenizer`.

fixes mishoo#1943
@alexlamsl alexlamsl merged commit 9464d3c into mishoo:master May 15, 2017
@alexlamsl alexlamsl deleted the issue-1943 branch May 15, 2017 21:40
@itsmepetrov
Copy link

@alexlamsl can you also ship this fix for 2.x version?

@alexlamsl
Copy link
Collaborator Author

@itsmepetrov this will be backported to v2.x indeed.

@itsmepetrov
Copy link

@alexlamsl good) Can you push the new version to npm?

@alexlamsl
Copy link
Collaborator Author

We still release 2.x versions of uglify-js on npm, yes 😉

Will probably take a hour or so while Travis CI verifies everything though.

@itsmepetrov
Copy link

Ok, thanks 👍

alexlamsl added a commit to alexlamsl/UglifyJS that referenced this pull request May 15, 2017
Account for comments when detecting property access in `tokenizer`.

fixes mishoo#1943
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.

2.8.25 produces an error in React Native build
4 participants