BrainCrumbz
BrainCrumbz
Thanks to you for your time
@cjk7989 thanks for the additional info on content size. Although in our case we were exceeding the Standard SKU max content size too.
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 `npm install`, it says that package-lock.json file was created with an old version...
Thanks for your info. Is that a Windows machine?
Yes we see that warning on package-lock too. Just for completeness: * we tried with video.js v8.2.0 as well as most recent commit, 35c539d * we tried both on windows...
ok, just checked on [Sass guide](https://sass-lang.com/documentation/at-rules/import), the underscore is expected
As a (temporary?) workaround this is the change that enabled us to build and test successfully: ```scss @import "../../node_modules/videojs-font/scss/icons"; ```
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 `build:css:cdn` and `build:css:default` tasks in `package.json`. Only modifying...
Hi there just tried with these changes, the way you suggested:  `npm run build` completed with no errors. Same for `npm run start`. Would that also work on Unix/MacOS...