Most people has stopped using bower. Even bower has posted deprecated notice on their website and npm.
Thus people started using yarn / npm for managing packages, even for those that are considered not JavaScript projects. (e.g. bootstrap-sass)
For convenience, our company has developed a build tool for building client-based project easily using TypeScript and Sass, which is then used across all teams: https://github.com/ryanelian/instapack
We configured the Sass compiler to look into node_modules folder when attempting to import a source code. For example:
This allows working with the npm repository using Sass, just like how you'd work with NuGet in C#. Very elegant.
Unfortunately, Visual Studio thinks that the imported files do not exist. This disables the programmer from fully utilizing F12 and intellisense.
mlorbetske
commented
7 years ago
Most people has stopped using
bower. Evenbowerhas posted deprecated notice on their website andnpm.Thus people started using
yarn/npmfor managing packages, even for those that are considered not JavaScript projects. (e.g.bootstrap-sass)For convenience, our company has developed a build tool for building client-based project easily using TypeScript and Sass, which is then used across all teams: https://github.com/ryanelian/instapack
We configured the Sass compiler to look into
node_modulesfolder when attempting to import a source code. For example:This allows working with the npm repository using Sass, just like how you'd work with NuGet in C#. Very elegant.
Unfortunately, Visual Studio thinks that the imported files do not exist. This disables the programmer from fully utilizing F12 and intellisense.
It would be nice to have this behavior somehow.