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

Expose scss file in "style" field of package.json #1045

Closed
ringods opened this issue Jun 11, 2016 · 1 comment
Closed

Expose scss file in "style" field of package.json #1045

ringods opened this issue Jun 11, 2016 · 1 comment
Labels
Milestone

Comments

@ringods
Copy link

ringods commented Jun 11, 2016

Hello,

I am trying use bootstrap-sass via npm, node-sass and the sass-module-importer. The importer documents this lookup strategy:

1. Set a SCSS/Sass/CSS file on the "main" field of their package.json/bower.json
2. Set a SCSS/Sass/CSS file on the "style" field of their package.json/bower.json
3. Have a index.css file on the root of their module

If I look at the bootstrap npm package, it uses the style field in package.json. It seems this field is becoming a de facto standard.

Is it possible to get a similar setup and expose the main scss file in the style field of package.json?

@cvrebert cvrebert changed the title Expose scss file in style field of package.json Expose scss file in "style" field of package.json Jun 17, 2016
@cvrebert
Copy link
Collaborator

We should also add a "sass" field for consistency with https://github.com/twbs/bootstrap/blob/ac1ea8c26ccb4b65d14bf207974854ca993ea4e5/package.json#L25

pads pushed a commit to talis/bootstrap-sass that referenced this issue Jul 20, 2016
* Add "style" field to package.json (twbs#1051); fixes twbs#1045

* Add "sass" field to package.json for consistency with upstream

Refs twbs#1045

* Create distribution
@glebm glebm added this to the v3.3.7 milestone Jul 25, 2016
ElMassimo pushed a commit to SolarCS/bootstrap-sass that referenced this issue Apr 11, 2017
ElMassimo pushed a commit to SolarCS/bootstrap-sass that referenced this issue Apr 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants