-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
(Still) Wrong path for font scss in video-js.scss on v8.0.4 #8149
Comments
Is there any workaround (even temporary) for this one? So that we can run tests and give a go to #8136 |
Is it possibile that issue is caused by using a different version of npm? When we run |
@BrainCrumbz I just tested to see if we could possibly run into the same error. However, I did not encounter this issue. But maybe I didn't follow the procedure as described. Here is what I did:
Everything went smoothly, see the logs: > [email protected] build:css
> npm-run-all build:css:*
> [email protected] build:css:cdn
> sass --load-path='./' --load-path='./node_modules/' --no-source-map src/css/vjs-cdn.scss dist/alt/video-js-cdn.css
> [email protected] postbuild:css:cdn
> postcss --verbose --config postcss.config.js -d dist/alt dist/alt/video-js-cdn.css
Processing dist/alt/video-js-cdn.css...
Finished dist/alt/video-js-cdn.css in 260 ms
> [email protected] build:css:default
> sass --load-path='./' --load-path='./node_modules/' --no-source-map src/css/vjs.scss dist/video-js.css
> [email protected] postbuild:css:default
> postcss --verbose --config postcss.config.js -d dist/ dist/video-js.css
Processing dist/video-js.css...
Finished dist/video-js.css in 247 ms |
Same result with > [email protected] build:css
> npm-run-all build:css:*
> [email protected] build:css:cdn
> sass --load-path='./' --load-path='./node_modules/' --no-source-map src/css/vjs-cdn.scss dist/alt/video-js-cdn.css
> [email protected] postbuild:css:cdn
> postcss --verbose --config postcss.config.js -d dist/alt dist/alt/video-js-cdn.css
Processing dist/alt/video-js-cdn.css...
Finished dist/alt/video-js-cdn.css in 252 ms
> [email protected] build:css:default
> sass --load-path='./' --load-path='./node_modules/' --no-source-map src/css/vjs.scss dist/video-js.css
> [email protected] postbuild:css:default
> postcss --verbose --config postcss.config.js -d dist/ dist/video-js.css
Processing dist/video-js.css...
Finished dist/video-js.css in 254 ms
|
Thanks for your info. Is that a Windows machine? |
@BrainCrumbz I'm using an Ubuntu 22.04 machine. I add the following warning, since the package-lock was generated with an "older" npm version. But it shouldn't have any side effect. npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile Did you try to delete the |
Yes we see that warning on package-lock too. Just for completeness:
with no effect on the issue. What are the contents of videojs-icons.scss
_icons.scss and I don't know if that's consistent with the code importing: @import "videojs-font/scss/icons"; I mean, there's no file named |
ok, just checked on Sass guide, the underscore is expected |
As a (temporary?) workaround this is the change that enabled us to build and test successfully: @import "../../node_modules/videojs-font/scss/icons";
|
I had the same problem with my project using lerna to manage packages |
I had the same problem and managed to fix it by removing before: "build:css:cdn": "sass --load-path='./' --load-path='./node_modules/' --no-source-map src/css/vjs-cdn.scss dist/alt/video-js-cdn.css", after "build:css:cdn": "sass --load-path=./ --load-path=./node_modules/ --no-source-map src/css/vjs-cdn.scss dist/alt/video-js-cdn.css", But i'm not sure about its side effect Windows 11 |
@fauzi9331 's solution works for me as well. Remove the quotes around the "load paths" for both Windows 10 |
We just forked main today, so video.js is 8.11.8. Following @ahm23 integrations worked for us, that is: we had to modify both Windows 11, 23H2 |
Do escaped double quotes work on people's environments that have problems with single quotes?, e.g. |
I think that should work everywhere, yes |
Good news. If you need some more tests on Windows, we could try. Also WSL with Ubuntu. |
Description
Apparently we met the issue mentioned at #7863 .
Reduced test case
No response
Steps to reproduce
npm install
npm test
. Also, one can runnpm run build
afterwards.Expected result:
All should be fine.
Actual result:
scripts show errors.
Errors
The errors seem the same for test or build.
What version of Video.js are you using?
8.0.4 up to commit a27ee05
Video.js plugins used.
None
What browser(s) including version(s) does this occur with?
None. This is from command line
What OS(es) and version(s) does this occur with?
Windows 11
npm 9.3.1
node v18.14.0
Both from windows command line as well as WSL terminal.
The text was updated successfully, but these errors were encountered: