Comments (7)
It might be better to find dist -delete
instead. If the directory doesn't exist it's just a no-op and won't scribble to stderr.
from hls.js.
@tjenkinson would you mind rechecking with latest hls.js/master ?
clean and test should work
regarding Hls not exported, it might be solved by https://github.com/dailymotion/hls.js/pull/17
from hls.js.
closing as should be fixed and no additional complaints received for a month now :-)
plz reopen with fresh logs in case any issue persists.
from hls.js.
Sorry I missed your previous message about building. I'll give it a try later!
On 26 Oct 2015, at 11:20, Guillaume du Pontavice [email protected] wrote:
closing as should be fixed and no additional complaints received for a month now :-)
plz reopen with fresh logs in case any issue persists.โ
Reply to this email directly or view it on GitHub.
from hls.js.
This is the output I get when I run npm run build
with http://babun.github.io/
{ hls.js } master ยป npm run build /cygdrive/c/Users/Thoma/Documents/GitHub/hls.js
> [email protected] prebuild C:\Users\Thoma\Documents\GitHub\hls.js
> npm run clean & npm run test
> [email protected] clean C:\Users\Thoma\Documents\GitHub\hls.js
> find dist -mindepth 1 -delete
> [email protected] pretest C:\Users\Thoma\Documents\GitHub\hls.js
> npm run lint
> [email protected] lint C:\Users\Thoma\Documents\GitHub\hls.js
> jshint src/
src\utils\xhr-loader.js: line 30, col 108, 'frag' is defined but never used.
1 error
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "lint"
npm ERR! node v0.12.7
npm ERR! npm v2.11.3
npm ERR! code ELIFECYCLE
npm ERR! [email protected] lint: `jshint src/`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the [email protected] lint script 'jshint src/'.
npm ERR! This is most likely a problem with the hls.js package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! jshint src/
npm ERR! You can get their info via:
npm ERR! npm owner ls hls.js
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! C:\Users\Thoma\Documents\GitHub\hls.js\npm-debug.log
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "test"
npm ERR! node v0.12.7
npm ERR! npm v2.11.3
npm ERR! code ELIFECYCLE
npm ERR! [email protected] pretest: `npm run lint`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] pretest script 'npm run lint'.
npm ERR! This is most likely a problem with the hls.js package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! npm run lint
npm ERR! You can get their info via:
npm ERR! npm owner ls hls.js
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! C:\Users\Thoma\Documents\GitHub\hls.js\npm-debug.log
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "build"
npm ERR! node v0.12.7
npm ERR! npm v2.11.3
npm ERR! code ELIFECYCLE
npm ERR! [email protected] prebuild: `npm run clean & npm run test`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] prebuild script 'npm run clean & npm run test'.
npm ERR! This is most likely a problem with the hls.js package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! npm run clean & npm run test
npm ERR! You can get their info via:
npm ERR! npm owner ls hls.js
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! C:\Users\Thoma\Documents\GitHub\hls.js\npm-debug.log
If I remove the npm run test
from the prebuild
step in package.json
then it builds fine, so there are still issues, but it is possible to get it to build now with a tweak :)
from hls.js.
thanks for rechecking, most probably the issue is related to the lint error, which fix has just been merged, see https://github.com/dailymotion/hls.js/pull/41, if by any chance you could update and confirm that everything is now working without any tweak ?
thanks in advance ๐
from hls.js.
Hi.
I am having a similar problem in Windows 10.
I have tried removing the npm run test from the prebuild step in package.json, but still no joy.
Here is the npm-debug.log:
0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files (x86)\nodejs\node.exe',
1 verbose cli 'C:\Program Files (x86)\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'dev' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'predev', 'dev', 'postdev' ]
5 info predev [email protected]
6 info dev [email protected]
7 verbose unsafe-perm in lifecycle true
8 info [email protected] Failed to exec dev script
9 verbose stack Error: [email protected] dev: npm run build && npm run open -s & parallelshell 'npm run live-reload -s' 'npm run serve -s' 'npm run watch -s'
9 verbose stack Exit status 1
9 verbose stack at EventEmitter. (C:\Program Files (x86)\nodejs\node_modules\npm\lib\utils\lifecycle.js:217:16)
9 verbose stack at emitTwo (events.js:87:13)
9 verbose stack at EventEmitter.emit (events.js:172:7)
9 verbose stack at ChildProcess. (C:\Program Files (x86)\nodejs\node_modules\npm\lib\utils\spawn.js:24:14)
9 verbose stack at emitTwo (events.js:87:13)
9 verbose stack at ChildProcess.emit (events.js:172:7)
9 verbose stack at maybeClose (internal/child_process.js:827:16)
9 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
10 verbose pkgid [email protected]
11 verbose cwd C:\Users\rohan.leach\Downloads\hls.js
12 error Windows_NT 10.0.10586
13 error argv "C:\Program Files (x86)\nodejs\node.exe" "C:\Program Files (x86)\nodejs\node_modules\npm\bin\npm-cli.js" "run" "dev"
14 error node v4.4.2
15 error npm v2.15.0
16 error code ELIFECYCLE
17 error [email protected] dev: npm run build && npm run open -s & parallelshell 'npm run live-reload -s' 'npm run serve -s' 'npm run watch -s'
17 error Exit status 1
18 error Failed at the [email protected] dev script 'npm run build && npm run open -s & parallelshell 'npm run live-reload -s' 'npm run serve -s' 'npm run watch -s''.
18 error This is most likely a problem with the hls.js package,
18 error not with npm itself.
18 error Tell the author that this fails on your system:
18 error npm run build && npm run open -s & parallelshell 'npm run live-reload -s' 'npm run serve -s' 'npm run watch -s'
18 error You can get information on how to open an issue for this project with:
18 error npm bugs hls.js
18 error Or if that isn't available, you can get their info via:
18 error
18 error npm owner ls hls.js
18 error There is likely additional logging output above.
19 verbose exit [ 1, true ]
from hls.js.
Related Issues (20)
- does hls.js support data uri for playback? HOT 1
- Allow getting the current URL HOT 4
- CHUNK_DEMUXER_ERROR_APPEND_FAILED when playing HEVC video stream HOT 2
- fragParsingError Demux HOT 1
- HLS fails to stream video with name containing U+3000 character. HOT 2
- Adding HLS subtitles separately HOT 2
- When I start my server and stream from OBS, the video loads ~10 sec backwards. HOT 9
- CMCD "nor" and "d" should return part details during Low-Latency HLS streaming
- The problem of drawing frame images on the canvas HOT 7
- Duplicate Captions for MP4 Content HOT 10
- Can I work with frames or merge fragments before play? HOT 3
- Stream freeze issue on reload HOT 1
- Disabling inflight subtitle playlist prevents segments from ever loading HOT 3
- Google chrome vs H.264 recovery point SEI HOT 1
- Cookies are not sent when requesting a TS HOT 1
- LG C1 WebOS and KONKA A55 WebOS hls.js Dolby Vision does not respond HOT 7
- bitrate hjs.js
- Rendition selection with multi-codec manifest could ignore the preferred codec HOT 1
- Only play the first five seconds even if audio is longer HOT 3
- `internal-error` in `keystatuseschange` is not handled well
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. ๐๐๐
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google โค๏ธ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from hls.js.