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.

Document public Sass API for v10

See original GitHub issue

In the past, we’ve exposed our Sass API in general for folks to use. As we are guarding against breaking changes, this has been causing troubles when it comes to build breakage. As a result, we should document our public Sass API in src/globals/scss/README.md (at least initially) as a point of reference for people to understand what we support from the Sass perspective.

Issue Analytics

State:
Created 5 years ago
Comments:9 (8 by maintainers)

Top GitHub Comments

1reaction

joshblackcommented, Feb 18, 2019

That’s a bummer 😞 definitely agreed though, this would help out a lot. Will make sure to add it to elements as well 👍

0reactions

carbon-botcommented, Mar 21, 2019

🎉 This issue has been resolved in version 9.87.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Top Results From Across the Web

Remove public scss api · Issue #4980 · Shopify/polaris - GitHub

Remove the src/styles/_public-api.scss file Remove the build script that copies the public API to the npm package Document the removal of the public...

sass | JS API

The JavaScript API provides two entrypoints for compiling Sass to CSS, each of which has a synchronous variant that returns a plain CompileResult...

Frameworks - Carbon Design System

The library provides front-end developers & engineers a collection of reusable HTML and SCSS partials to build websites and user interfaces.

node-sass - npm

Start using node-sass in your project by running `npm i node-sass`. ... node-sass. 8.0.0 • Public • Published 2 months ago.

Node Sass couldn't find a binding for your current environment

Node: v10.7.0 node-sass: v3.13.1 . Says my current environment is 32 bit windows with node 0.10.x which is simply not true ...