SCSS Same Level bug is back on Windows
In reference to existing closed tickets, this bug has just occurred once again, and cost me about 4 hours trying to figure out why 🙃. If possible it may be worth putting a message into the error stream to advise of this as a known issue on the "file not found" exception.
Current closed ticket links: #387 #404
In below code block are the current package.json imports:
"dependencies": {
"@andxor/jquery-ui-touch-punch-fix": "^1.0.2",
"@bigcommerce/stencil-utils": "^6.17.0",
"aos": "^2.3.4",
"baguettebox.js": "^1.12.0",
"clipboard-cli": "^4.0.0",
"core-js": "^3.38.1",
"creditcards": "^5.0.0",
"font-awesome": "^4.7.0",
"foundation-sites": "^5.5.3",
"in-view": "^0.6.1",
"jquery": "^3.7.1",
"jquery-ui": "^1.14.0",
"js-cookie": "^3.0.5",
"jstree": "^3.3.17",
"lazysizes": "5.3.2",
"lodash": "^4.17.21",
"mustache": "^4.2.0",
"nod-validate": "^2.0.12",
"object-fit-images": "^3.2.4",
"posthog-js": "^1.165.0",
"regenerator-runtime": "^0.14.1",
"scroll-to-element": "^2.0.3",
"selectize": "^0.12.6",
"slick-carousel": "^1.8.1",
"svg-injector": "^1.1.3",
"sweetalert2": "^11.14.1",
"webfontloader": "^1.6.28",
"whatwg-fetch": "^3.6.20",
"wicg-inert": "^3.1.3"
},
"devDependencies": {
"@babel/core": "^7.25.2",
"@babel/plugin-syntax-dynamic-import": "^7.8.3",
"@babel/preset-env": "^7.25.4",
"@bigcommerce/citadel": "^2.15.1",
"babel-eslint": "^10.1.0",
"babel-jest": "^29.7.0",
"babel-loader": "^9.2.1",
"babel-plugin-lodash": "^3.3.4",
"clean-webpack-plugin": "^4.0.0",
"cli": "^1.0.1",
"css-loader": "^7.1.2",
"cssnano": "^7.0.6",
"eslint": "^4.8.0",
"eslint-config-airbnb": "^16.0.0",
"eslint-plugin-import": "^2.30.0",
"eslint-plugin-jsx-a11y": "^6.10.0",
"eslint-plugin-react": "^7.37.0",
"expose-loader": "^4.0.0",
"grunt": "^1.6.1",
"grunt-cli": "^1.5.0",
"grunt-contrib-clean": "^2.0.1",
"grunt-contrib-copy": "^1.0.0",
"grunt-eslint": "^20.0.0",
"grunt-run": "^0.8.1",
"grunt-stylelint": "^0.16.0",
"grunt-svgstore": "^2.0.0",
"grunt-text-replace": "^0.4.0",
"imports-loader": "^5.0.0",
"jest": "^29.7.0",
"lighthouse": "^12.2.1",
"load-grunt-config": "^4.0.1",
"lodash-webpack-plugin": "^0.11.6",
"style-loader": "^2.0.0",
"stylelint": "^13.9.0",
"stylelint-config-sass-guidelines": "^7.1.0",
"stylelint-scss": "^3.18.0",
"time-grunt": "^2.0.0",
"url": "^0.11.4",
"webpack": "^5.95.0",
"webpack-bundle-analyzer": "^4.10.2",
"webpack-cli": "^5.1.4",
"webpack-merge": "^6.0.1"
}
Environment
Stencil-cli version stencil --version:
8.4.0 (latest at time of publication)
Node version node -v:
v20.17.0
NPM version npm -v:
10.8.3
OS: Windows 10 (Latest Patch)
Can you post a case how to reproduce and what error was observed?
Hey @jairo-bc
As per initial bug report, the findings are as per the referenced previous cases. It appears that this bug has reappeared, with the same root cause most likely.
Root cause is unknown to me at this time, but symptoms are the same as previous cases; and the "stop gap remedy" is the same.
If this issue is not replicable with the default stencil theme, I can privately send you the project files for our theme where the issue was noticed.
- Jordan