rm node_modules

2 files changed, 0 insertions, 119 deletions

diff --git a/node_modules/node-sass/src/libsass/.github/CONTRIBUTING.md b/node_modules/node-sass/src/libsass/.github/CONTRIBUTING.md
deleted file mode 100644
index 2ff99d8..0000000
--- a/node_modules/node-sass/src/libsass/.github/CONTRIBUTING.md
+++ /dev/null
@@ -1,65 +0,0 @@
-# Contributing to LibSass
-
-:+1::tada: First off, thanks for taking the time to contribute! :tada::+1:
-
-The following is a set of guidelines for contributing to LibSass, which is hosted in the [Sass Organization](https://github.com/sass) on GitHub.
-These are just guidelines, not rules, use your best judgment and feel free to propose changes to this document in a pull request.
-
-LibSass is a library that implements a [sass language][8] compiler. As such it does not directly interface with end users (frontend developers).
-For direct contributions to the LibSass code base you will need to have at least a rough idea of C++, we will not lie about that.
-But there are other ways to contribute to the progress of LibSass. All contributions are done via github pull requests.
-
-You can also contribute to the LibSass [documentation][9] or provide additional [spec tests][10] (and we will gladly point you in the
-direction for corners that lack test coverage). Foremost we rely on good and concise bug reports for issues the spec tests do not yet catch.
-
-## Precheck: My Sass isn't compiling
-- [ ] Check if you can reproduce the issue via [SourceMap Inspector][5] (updated regularly).
-- [ ] Validate official ruby sass compiler via [SassMeister][6] produces your expected result.
-- [ ] Search for similar issue in [LibSass][1] and [node-sass][2] (include closed tickets)
-- [ ] Optionally test your code directly with [sass][7] or [sassc][3] ([installer][4])
-
-## Precheck: My build/install fails
-- [ ] Problems with building or installing libsass should be directed to implementors first!
-- [ ] Except for issues directly verified via sassc or LibSass own build (make/autotools9
-
-## Craft a meaningfull error report
-- [ ] Include the version of libsass and the implementor (i.e. node-sass or sassc)
-- [ ] Include information about your operating system and environment (i.e. io.js)
-- [ ] Either create a self contained sample that shows your issue ...
-- [ ] ... or provide it as a fetchable (github preferred) archive/repo
-- [ ] ... and include a step by step list of command to get all dependencies
-- [ ] Make it clear if you use indented or/and scss syntax
-
-## My error is hiding in a big code base
-1. we do not have time to support your code base!
-2. to fix occuring issues we need precise bug reports
-3. the more precise you are, the faster we can help you
-4. lazy reports get overlooked even when exposing serious bugs
-5. it's not hard to do, it only takes time
-- [ ] Make sure you saved the current state (i.e. commit to git)
-- [ ] Start by uncommenting blocks in the initial source file
-- [ ] Check if the problem is still there after each edit
-- [ ] Repeat until the problem goes away
-- [ ] Inline imported files as you go along
-- [ ] Finished once you cannot remove more
-- [ ] The emphasis is on the word "repeat" ...
-
-## What makes a code test case
-
-Important is that someone else can get the test case up and running to reproduce it locally. For this
-we urge you to verify that your sample yields the expected result by testing it via [SassMeister][6]
-or directly via ruby sass or node-sass (or any other libsass implementor) before submitting your bug
-report. Once you verified all of the above, you may use the template below to file your bug report.
-
-
-[1]: https://github.com/sass/libsass/issues?utf8=%E2%9C%93&q=is%3Aissue
-[2]: https://github.com/sass/node-sass/issues?utf8=%E2%9C%93&q=is%3Aissue
-[3]: https://github.com/sass/sassc
-[4]: http://libsass.ocbnet.ch/installer/
-[5]: http://libsass.ocbnet.ch/srcmap/
-[6]: http://www.sassmeister.com/
-[7]: https://rubygems.org/gems/sass
-
-[8]: http://sass-lang.com/
-[9]: https://github.com/sass/libsass/tree/master/docs
-[10]: https://github.com/sass/sass-spec
diff --git a/node_modules/node-sass/src/libsass/.github/ISSUE_TEMPLATE.md b/node_modules/node-sass/src/libsass/.github/ISSUE_TEMPLATE.md
deleted file mode 100644
index 43ffaaa..0000000
--- a/node_modules/node-sass/src/libsass/.github/ISSUE_TEMPLATE.md
+++ /dev/null
@@ -1,54 +0,0 @@
-[todo]: # (Title: Be as meaningful as possible)
-[todo]: # (Title: Try to use 60 or less chars)
-
-[todo]: # (This is only a template!)
-[todo]: # (remove unneeded bits)
-[todo]: # (use github preview!)
-
-## input.scss
-
-[todo]: # (always test and report with scss syntax)
-[todo]: # (use sass only when results differ from scss)
-
-```scss
-test {
-  content: bar
-}
-```
-
-## Actual results
-
-[todo]: # (update version info!)
-
-[libsass 3.X.y][1]
-```css
-test {
-  content: bar; }
-```
-
-## Expected result
-
-[todo]: # (update version info!)
-
-ruby sass 3.X.y
-```css
-test {
-  content: bar; }
-```
-
-[todo]: # (update version info!)
-[todo]: # (example for node-sass!)
-
-version info:
-```cmd
-$ node-sass --version
-node-sass       3.X.y   (Wrapper)       [JavaScript]
-libsass         3.X.y   (Sass Compiler) [C/C++]
-```
-
-[todo]: # (Go to http://libsass.ocbnet.ch/srcmap)
-[todo]: # (Enter your SCSS code and hit compile)
-[todo]: # (Click `bookmark` and replace the url)
-[todo]: # (link is used in actual results above)
-
-[1]: http://libsass.ocbnet.ch/srcmap/#dGVzdCB7CiAgY29udGVudDogYmFyOyB9Cg==