videojs-swf
Advanced tools
Comparing version 4.4.0 to 4.4.1
{ | ||
"name": "videojs-swf", | ||
"description": "The Flash-fallback video player for video.js (http://videojs.com)", | ||
"version": "4.4.0", | ||
"version": "4.4.1", | ||
"copyright": "Copyright 2014 Brightcove, Inc. https://github.com/videojs/video-js-swf/blob/master/LICENSE", | ||
@@ -19,3 +19,3 @@ "keywords": [ | ||
"async": "~0.2.9", | ||
"flex-sdk": "4.6.0", | ||
"flex-sdk": "4.6.0-0", | ||
"video.js": "4.3.0", | ||
@@ -22,0 +22,0 @@ "grunt-cli": "~0.1.0", |
@@ -9,34 +9,25 @@ The light-weight Flash video player that makes Flash work like HTML5 video. This allows player skins, plugins, and other features to work with both HTML5 and Flash | ||
1. Install Node Packages. | ||
```bash | ||
npm install | ||
``` | ||
2. Compile SWF. | ||
Development (places new SWF in /dist/): | ||
```bash | ||
grunt mxmlc | ||
``` | ||
Production/ Distribution (runs mxmlc task and copies SWF to dist/): | ||
```bash | ||
grunt dist | ||
``` | ||
3. Run Connect Server. | ||
```bash | ||
grunt connect:dev | ||
``` | ||
4. Open your browser at [http://localhost:8000/index.html](http://localhost:8000/index.html) to see a video play. You can keep using grunt to rebuild the Flash code. | ||
8. Open your browser at [http://localhost:8000/index.html](http://localhost:8000/index.html) to see a video play. You can keep using grunt to rebuild the Flash code. | ||
Running Unit and Integration Tests | ||
=========== | ||
** Notes - We should drop all of this for grunt based / Karma testing. | ||
** Note - We want to drop all of this for grunt based / Karma testing. | ||
@@ -47,9 +38,4 @@ For unit tests, this project uses [FlexUnit](http://flexunit.org/). The unit tests can be found in [project root]/src/com/videojs/test/ | ||
In order to run all of the tests, run test.sh. | ||
In order to run all of the tests, use the links at [http://localhost:8000/index.html](http://localhost:8000/index.html) | ||
./test.sh | ||
A copy of the SWF produced for the unit tests will be compiled into the bin-debug folder. Both the unit and integration tests will attempt to run with the 'open' command, or an instruction will be given on how to run them manually. | ||
There are very few tests. Adding to them is a fantastic and much appreciated way to contribute. | ||
Sorry, the diff of this file is not supported yet
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Empty package
Supply chain riskPackage does not contain any code. It may be removed, is name squatting, or the result of a faulty package publish.
Found 1 instance in 1 package
Major refactor
Supply chain riskPackage has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.
Found 1 instance in 1 package
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
No License Found
License(Experimental) License information could not be found.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Misc. License Issues
License(Experimental) A package's licensing information has fine-grained problems.
Found 1 instance in 1 package
Shell access
Supply chain riskThis module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.
Found 1 instance in 1 package
0
19316
3
1
0
40
3