The first import that normalize does is for a file that does not exist. Any ideas?

It seems that in this commit f32a7fdae314297ee053d6588d7ea913aeb7fb4b , it was removed from the normalized folder.

Since the people cry for a world without dependencies, we should drop compass. Or, at least, we should stick together a version without compass.

For sure, there are a lot of great forks out there, but you are the leader at NPM, RubyGem etc.

After a bit of research I found this gist, which could help us: https://gist.github.com/ry5n/2026666

Version 4.1.0 of eslint just got published.

The version 4.1.0 is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of eslint. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Your Greenkeeper Bot :palm_tree:

From a fresh Bower install, and import of the normalize.scss files the following error is returned

Error: Undefined variable: "$px-fallback".
    on line 42 of bower_components/normalize-scss/fork-versions/default/_vertical-rhythm.scss, in `normalize-rhythm'
    from line 58 of bower_components/normalize-scss/fork-versions/default/_vertical-rhythm.scss, in `normalize-margin'
    from line 185 of bower_components/normalize-scss/fork-versions/default/_normalize.scss
    from line 2 of sass/style.scss

I was hoping to use this version of normalize as my default install for a static site generator I am working on, but then today as I was about to publish the first stable version and I could no longer compile the sass.

I was wondering if there was a new name in the bower registry? I guess I can specify the repo directly, but my yeoman generator will look pretty silly when the prompt stretches off the screen saying:

[?] Bower packages to install, comma separated: angular,[email protected]:JohnAlbin/normalize-scss.git

Any suggestions? Or can you re-publish on bower?

Hi,

I have installed the partial _normalize.scss but the compilation failed :

error sass/styles.sass (Line 192 of sass/vendors/_normalize.scss: 0.15em/px isn't a valid CSS value.)

It's looking like a problem with the rhythm mixin but I don't understand why...

Any idea ?

At least it looks that way: http://beta.compass-style.org/CHANGELOG/

When running alpha versions of Compass 1.0.0 a warning will be issued due to the fact that _normalize.scss sets $legacy-support-for-ie6 and $legacy-support-for-ie7. I solved this problem by simply moving the variables below the compass imports around line 42 since they are still expected later on in _normalize.scss. Of course, for people wanting legacy IE support this probably isn't the best solution as Compass itself isn't being configured.

The warning issued when compiling:

WARNING: Compass has changed how browser support is configured. See the CHANGELOG for more details. The following configuration variables are no longer supported: $legacy-support-for-ie6, $legacy-support-for-ie7.

Much like with my other pull request, I could be barking up the wrong tree here, but I figured, for code such as the example below, this would prevent huge, unneeded, margins on each of the inner lists:

<ul>
    <li>TV Series
        <ul>
            <li>TV Series DVD</li>
            <li>TV Series Bluray</li>
        </ul>
    </li>
    <li>Movies
        <ul>
            <li>DVD Movies</li>
            <li>Bluray Movies</li>
        </ul>
    </li>
    <li>Games
        <ul>
            <li>PC
                <ul>
                    <li>Download from Steam</li>
                    <li>Physical Media</li>
                </ul>
            </li>
            <li>Xbox 360</li>
            <li>Playstation 3</li>
        </ul>
    </li>
</ul>

(Or maybe this should be submitted to the original normalize.css project, I don't know)

ERROR in ./src/sass/mvxtheme.scss
Module build failed: ModuleBuildError: Module build failed:
    @error "The normalize vertical-rhythm module only supports px inputs. The typey library is better.";
   ^
      The normalize vertical-rhythm module only supports px inputs. The typey library is better.
      in /mnt/c/Users/garfi/Documents/GitHub/.../node_modules/normalize-scss/sass/normalize/_vertical-rhythm.scss (line 10, column 5)
    at runLoaders (/mnt/c/Users/garfi/Documents/GitHub/.../node_modules/webpack/lib/NormalModule.js:194:19)
    at /mnt/c/Users/garfi/Documents/GitHub/.../node_modules/loader-runner/lib/LoaderRunner.js:364:11
    at /mnt/c/Users/garfi/Documents/GitHub/.../node_modules/loader-runner/lib/LoaderRunner.js:230:18
    at context.callback (/mnt/c/Users/garfi/Documents/GitHub/.../node_modules/loader-runner/lib/LoaderRunner.js:111:13)
    at Object.asyncSassJobQueue.push [as callback] (/mnt/c/Users/garfi/Documents/GitHub/.../node_modules/sass-loader/lib/loader.js:55:13)
    at Object.<anonymous> (/mnt/c/Users/garfi/Documents/GitHub/.../node_modules/async/dist/async.js:2244:31)
    at Object.callback (/mnt/c/Users/garfi/Documents/GitHub/.../node_modules/async/dist/async.js:906:16)
    at options.error (/mnt/c/Users/garfi/Documents/GitHub/.../node_modules/node-sass/lib/index.js:294:32)
 @ ./src/index.js 3:0-26

mvxtheme.scss

@import '~normalize-scss/sass/_normalize.scss';
@include normalize();

Hi,

maybe I'm completely lost, but when I look at your bower.json the normalize/_import-now.scss file is marked as main file.

There are some instructions on how to use your lib, but there is no real scenario on how to use it with bower, except of the note that you have to override some things to use it with wiredep.

We want to use css libs from our project by just running bower install and adding an @import line in our main css.

In your case, the main file is in the ./normalize Folder. Normally other css libraries use the main file in the root namespace but you don't, so we can't use your Project in the same generic way with Sass include paths.

If there is nothing against from your side using the normalize-scss/sass/_normalize.scss instead of normalize-scss/sass/normalize/_import-now.scss you'd help us and properly all wiredeps user as well.

If you agree to that, I can open a PR.

Greets `Alwin Mark

When following the instructions to install/use the latest branch with support for normalize.css v3, Sass 3.3 and Compass 1.0 via bower there is an error resolving the target version. Presumably because the tag is missing?

$ bower install --save normalize.scss#3.0.0-alpha.2+normalize.3.0.0
bower normalize.scss#3.0.0-alpha.1+normalize.2.1.3       not-cached git://github.com/JohnAlbin/normalize-scss.git#3.0.0-alpha.1+normalize.2.1.3
bower normalize.scss#3.0.0-alpha.1+normalize.2.1.3          resolve git://github.com/JohnAlbin/normalize-scss.git#3.0.0-alpha.1+normalize.2.1.3
bower normalize.scss#3.0.0-alpha.2+normalize.3.0.0       not-cached git://github.com/JohnAlbin/normalize-scss.git#3.0.0-alpha.2+normalize.3.0.0
bower normalize.scss#3.0.0-alpha.2+normalize.3.0.0          resolve git://github.com/JohnAlbin/normalize-scss.git#3.0.0-alpha.2+normalize.3.0.0
bower normalize.scss#3.0.0-alpha.1+normalize.2.1.3         download https://github.com/JohnAlbin/normalize-scss/archive/3.0.0-alpha.1+normalize.2.1.3.tar.gz
bower normalize.scss#3.0.0-alpha.1+normalize.2.1.3          extract archive.tar.gz
bower normalize.scss#3.0.0-alpha.1+normalize.2.1.3         resolved git://github.com/JohnAlbin/normalize-scss.git#3.0.0-alpha.1+normalize.2.1.3
bower normalize.scss#3.0.0-alpha.2+normalize.3.0.0     ENORESTARGET No tag found that was able to satisfy 3.0.0-alpha.2+normalize.3.0.0

Additional error details:
Available versions: 3.0.0-alpha.1+normalize.2.1.3, 2.2.0+normalize.2.1.3, 2.1.3, 2.1.2, 2.1.0, 2.0.1, 2.0.1+build.2

I was able to get the version I wanted using the following command:

$ bower install --save git://github.com/JohnAlbin/normalize-scss#master

in case it helps:

$ npm -v && bower -v && uname -v
1.3.24
1.2.8
Darwin Kernel Version 13.0.0: Thu Sep 19 22:22:27 PDT 2013; root:xnu-2422.1.72~6/RELEASE_X86_64

Since Dart Sass 1.33.0 deprecation warnings regarding using slash for divisions are printed to the console when using normalize-scss in the same project. In order to prepare for the Dart Sass 2.0.0 release and to make sure that normalize-scss can be used in the future, the affected code parts have to be updated.

A blog post on the topic can be found here: https://sass-lang.com/documentation/breaking-changes/slash-div.

The issue has already been reported in the main repository here: https://github.com/JohnAlbin/normalize-scss/issues/148.

This PR now aims to resolve that issue.

Expected behavior

No deprecation warnings in the console.

Actual behavior

dart-sass (v 1.34.0) is reporting deprecation warnings.

DEPRECATION WARNING: Using / for division is deprecated and will be removed in Dart Sass 2.0.0.

Recommendation: math.div($value, $relative-to)

More info and automated migrator: https://sass-lang.com/d/slash-div

╷ 16 │ @return ($value / $relative-to) * 1em; │ ^^^^^^^^^^^^^^^^^^^^^ ╵ node_modules/normalize-scss/sass/normalize/_vertical-rhythm.scss 16:14 normalize-rhythm() node_modules/normalize-scss/sass/normalize/_vertical-rhythm.scss 27:14 normalize-font-size() node_modules/normalize-scss/sass/normalize/_normalize-mixin.scss 108:7 normalize()

If $normalize-vertical-rhythm is set to false manually we should be able to change the value of variable without the $normalize-vertical-rhythm being overridden here:

  // If we've customized any font variables, we'll need extra properties.
  @if $base-line-height != 24px
    or $base-unit != 'em'
    or $h2-font-size != 1.5  * $base-font-size
    or $h3-font-size != 1.17 * $base-font-size
    or $h4-font-size != 1    * $base-font-size
    or $h5-font-size != 0.83 * $base-font-size
    or $h6-font-size != 0.67 * $base-font-size {
    $normalize-vertical-rhythm: true !global;
  }

The logic should first detect if $normalize-vertical-rhythm was set by the user and only overwrite it if not. A better default value, therefore, would be null. You could then check against null in the above and only force to true if so. If false, then honour the users choice and don't output.

The checks for @if $normalize-vertical-rhythm { would all still work as intended.

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The devDependency auto-changelog was updated from 1.16.4 to 2.0.0.

This version is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

Publisher: cookpete License: MIT

Find out more about this release.

Your Greenkeeper bot :palm_tree:

Expected behavior

No deprecation warnings in the console.

Actual behavior

dart-sass (v 1.17.2) is reporting deprecation warnings.

DEPRECATION WARNING: As of Dart Sass 2.0.0, !global assignments won't be able to
declare new variables. Consider adding `$_normalize-exclude: null` at the top level.

Steps to reproduce the behaviour

Use the official sass module instead of an unofficial node-sass module to compile the code.