Skip to content
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

Relative path for style.scss leads to "Internal Error: File to read not found or unreadable" error. #220

Open
aliakseimaniuk opened this issue Jan 2, 2018 · 1 comment

Comments

@aliakseimaniuk
Copy link

After update from 3.4.1 version to 3.4.7 version, we noticed that sassc.exe for Windows stopped to recognize the relative path to style.scss file.

During build process we receive an error:
Internal Error: File to read not found or unreadable: C:/project/tools/../scss/style.scss

Project structure:

project
|-- bin
     |-- sassc_3.4.7_windows_amd64.exe
|-- scss
     |-- style.scss
|-- static
     |-- style.css
|-- tools
     |-- build.cmd

The code from project's build file:

SET tools_dir=%~dp0
SET root=%tools_dir%..
SET bin=%root%\bin

for %%f in (%bin%\sassc*%PROCESSOR_ARCHITECTURE%.exe) do SET sassc=%%f

SET sassc_input=%root%\scss\style.scss
SET sassc_output=%root%\static\style.css
SET sassc_style=nested

ECHO Building scss ...
%sassc% --style %sassc_style% %sassc_input% %sassc_output% || ECHO ERROR while launching %sassc%. && EXIT /B 1
ECHO Build scss finished.
@aliakseimaniuk aliakseimaniuk changed the title Relative path for style.scss lead to "Internal Error: File to read not found or unreadable" error. Relative path for style.scss leads to "Internal Error: File to read not found or unreadable" error. Jan 2, 2018
@dtvn
Copy link

dtvn commented Dec 29, 2018

My version is v3.7.0 run on Alpine image for Docker also encounters this bug.

Internal Error: File to read not found or unreadable: src/sass:public
The screenshot is just for demonstrate the problem. This bug has been tested many time within may difference dir location.

It also doesn't for single file or full path.

Do you have any solution for this bug?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants