question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

IncludePath not working in current version

See original GitHub issue

Hi Team, Reason : It’s works with old node-sass 4.7.2, but it doesn’t work in node-sass 4.8.1 latest version. Can you please provide the solution for this issue. It throws error.

Error: File to import not found or unreadable: ‘…’

Note: It’s works with node-sass 4.7.2 version

var sass = require('gulp-sass'); pipe(sass({ outputStyle: 'expanded', **includePaths: path** })

Thanks, Jayaprakash K.

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:17

github_iconTop GitHub Comments

2reactions
xzyfercommented, May 8, 2019

~ imports are a webpack feature and are not part of the Sass language.

On Thu., 9 May 2019, 8:12 am Alex Barker, notifications@github.com wrote:

@import “~bootstrap/scss/functions”; should be @import “bootstrap/scss/functions”; as the ~ does not appear to resolve to node_modules using gulp.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/dlmanning/gulp-sass/issues/668#issuecomment-490669839, or mute the thread https://github.com/notifications/unsubscribe-auth/AAENSWD3KVJUFYSFPNUFDXDPUNF5XANCNFSM4EUZPYPQ .

2reactions
ErraticFoxcommented, Apr 2, 2018

@xzyfer I’ve tried using the path module get around using ./ or ../ but still no success. I’ve tried multiple different ways, a couple of which being this:

includePaths: [
    path.join(__dirname, 'node_modules')
]

and

includePaths: [
    'node_modules'
]

in my SCSS file I’m compiling, I have @import '@material/toolbar'; though I keep getting the error Error: File to import not found or unreadable: @material/toolbar.

Read more comments on GitHub >

github_iconTop Results From Across the Web

VSCode not recognizing includes from includepath
Show activity on this post. Visual Studio Code not changes build command itself, even if includePath changes. You should change build command ...
Read more >
How to Fix Include Path Error in C/C++ Files using ... - YouTube
How to fix vscode error: #include errors detected. Please update your includePath.***************************Free Document ...
Read more >
Include Path Error in VS code while running c cpp codes
include_path_error_in_vs_code #include_in_c_cppHeaders path not found error, Change Include path setting error in VS code, these kinds of ...
Read more >
Get Started with C++ and Mingw-w64 in Visual Studio Code
Get the latest version of Mingw-w64 via MSYS2, which provides up-to-date native builds of GCC, Mingw-w64, and other helpful C++ tools and libraries....
Read more >
Include Path Problems - Libraries - PlatformIO Community
Include Path Problems · my library is not recognized in my main.cpp file. Solved by moving my headers files from src to an...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found