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

Remove Closure Compiler #1940

Closed
wants to merge 3 commits into from
Closed

Remove Closure Compiler #1940

wants to merge 3 commits into from

Conversation

heff
Copy link
Member

@heff heff commented Mar 9, 2015

Replace Closure Compiler with UglifyJS and remove closure compiler specific files. Addresses #1586.

We could also remove the API step in the automated tests now that we're not mangling object properties, unless we think that could still be valuable. @videojs/core-committers?

heff added 3 commits March 6, 2015 13:21
Moved the vtt.js concatentation to before minification to support sourcemaps.
Added a better license comment that survives minification.
@@ -16,7 +17,12 @@ module.exports = function(grunt) {
combined = combined.replace(/GENERATED_CDN_VSN/g, grunt.vjsVersion.majorMinor);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

when we get browserify, there's a transform that does this automatically for us.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we still support dropping the patch number like we're doing here?

@heff
Copy link
Member Author

heff commented Mar 9, 2015

In the comments of the related issue we discussed changing the private vars to use the underscore-first naming convention. I can wrap that into this one, but I wanted to give people a chance to respond in case there's significant reliance on the current private vars that we should be aware of.

@gkatsev
Copy link
Member

gkatsev commented Mar 9, 2015

So much red!

@@ -293,14 +324,25 @@ module.exports = function(grunt) {
}
},
usebanner: {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is there a need for usebanner anymore? I believe uglify can do it for us.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I saw that but wanted the banner in the non-minified version too, including version and copyright. Sounds like we could use browserify to do var replacement here too instead.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can run the unminified code through uglify beautifier if we wanted to. But makes sense to keep banner.
Does uglify create sourcemaps? If so, this could mess up with that if it is run after uglify.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's run before uglify, and uses the @license tag which uglify will preserve.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, cool.

@gkatsev
Copy link
Member

gkatsev commented Mar 9, 2015

This keeps the current file naming scheme, right?

@heff
Copy link
Member Author

heff commented Mar 9, 2015

It does keep the current file naming. That's a separate issue but I could easily wrap it into this one. That's one of those things I could see getting annoying when switching between 4.0 and 5.0 work, so we could also wait until closer to release. I could go either way.

@heff
Copy link
Member Author

heff commented Mar 11, 2015

I added a wiki page for tracking the details (what changed and why) of any API or process changes in 5.0. If we keep this up as we go it will be easier to put together communication around the 5.0 release.
https://github.com/videojs/video.js/wiki/5.0-Change-Details

@mmcc
Copy link
Member

mmcc commented Mar 12, 2015

lgtm

@heff heff closed this in 9dea6be Mar 12, 2015
@gkatsev
Copy link
Member

gkatsev commented Mar 16, 2015

🎉

@Grabilla
Copy link

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.

4 participants