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

Add: Notes on Webpack Fixes in React Docs #4261

Merged
merged 5 commits into from
Apr 12, 2017
Merged

Add: Notes on Webpack Fixes in React Docs #4261

merged 5 commits into from
Apr 12, 2017

Conversation

MCDELTAT
Copy link
Contributor

@MCDELTAT MCDELTAT commented Apr 6, 2017

Note how to require the css file, as denoted in the FAQ sections and clarification on how to resolve the .eot files in the css file.

Note how to require the css file, as denoted in the FAQ sections and clarification on how to resolve the .eot files in the css file.
@gkatsev
Copy link
Member

gkatsev commented Apr 7, 2017

Thanks @MCDELTAT, I wonder though if we should move it to a separate webpack.md file since the recommendations provided aren't react-specific. We'd also want to update the FAQ to point at that doc as well. Thoughts?

@MCDELTAT
Copy link
Contributor Author

MCDELTAT commented Apr 7, 2017

Sure. I'll do that later today.

@MCDELTAT
Copy link
Contributor Author

MCDELTAT commented Apr 7, 2017

In addition to the fixes already in place I also figured out how to use videojs-contrib-hls in te same setup. Should I create a webpack document there about the subject or combine all webpack related fixes in one doc?

MCDELTAT added 2 commits April 8, 2017 17:32
Removed references to Webpack from the React guide and moved them to a new Webpack guide. It also adds help on the configuration needed to use videojs-contrib-hls with Webpack.
Now refferences the new Webpack guide, alphabetized the links at the bottom for ease of future revision.
@gkatsev
Copy link
Member

gkatsev commented Apr 12, 2017

Keeping it here for contrib-hls is probably fine, though, we'd probably want to document it for HLS as well.

Also, is the change at the bottom of the FAQ just sorting of the links?

@@ -0,0 +1,37 @@
# Using Webpack with Video.js

video.js, and the playback technologies such as videojs-contrib-hls all work in a Webpack based build environment. Here are several configuration changes specific to Webpack that will get you up and running. The following guide was written and tested for videojs v15.9.1 and videojs-contrib-hls v5.4.0
Copy link
Member

Choose a reason for hiding this comment

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

I'm not sure it's necessary to specify the versions used. It should work with all versions


video.js, and the playback technologies such as videojs-contrib-hls all work in a Webpack based build environment. Here are several configuration changes specific to Webpack that will get you up and running. The following guide was written and tested for videojs v15.9.1 and videojs-contrib-hls v5.4.0

### Video.js CSS:
Copy link
Member

Choose a reason for hiding this comment

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

these headings should be ##, but I can always change that before merging.

@MCDELTAT
Copy link
Contributor Author

Ok. Yes the bottom of the page is just sorting the links alphabetically. I guess my OCD kicked in. I took the time to verify all the links still worked as well. I'll change those to ## right now.

I think I left the versions in just because contrib-hls states that you need to add videojs-flash as well if you use v6.0. I can remove that if you want as well.

This removes refferences to versions that this guide was tested on, and changes the header sizes from ### to ##.
@gkatsev
Copy link
Member

gkatsev commented Apr 12, 2017

Heh, it's fine. Just took me a while to figure out what was going on and wanted confirmation :D

@gkatsev gkatsev merged commit 230743e into videojs:master Apr 12, 2017
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.

3 participants