Any plans to make Normalize eyeglass compatible?

[ashleynolan]

I was just wondering if there was any plan to make the NPM module of Normalize compatible with Eyeglass?

I’ve seen there’s a sass version of normalize which is eyeglass compatible, but all I really want to pull into my projects is the straight up Normalize CSS, so was wondering if this was planned, or whether it would be worth me forking the repo and making a module that does this. Alternatively, I’d be happy to submit a PR to add this, if it would be something that you’d want to look to include.

Thanks for all the great work on the project.

[battaglr]

@ashleynolan, it's really hard to keep track of all these tools coming up. What changes would be necessary to support this?

[ashleynolan]

I’ll try and get something working in a fork so that I can see exactly what needs to be done and link to it as an example. Will post back here once I’ve done that (will be in the next couple of days)

[battaglr]

@ashleynolan, no need to code anything at this point. I just wanted to know if we need to include a new file, an entry on the package.json or something else.

[ashleynolan]

You can do it in a couple of ways, but the easiest is by including a few lines in the package.json.

You need to add "eyeglass-module" as a keyword and then a set of eyeglass options (like this).

Then after adding these, it should be possible to install Normalise via NPM and include it in a Sass build by just referencing @import normalise (or whatever import keyword you give it in the package.json).

[battaglr]

@ashleynolan, great that's great info, thank you! @jonathantneal, what do you think about this?

[kevva]

I wonder why authors to these tools are trying to make module authors adapt to them rather than the other way. One would expect that eyeglass somehow could make use of the main field instead when no other options exists or whatever.

[battaglr]

@kevva, I wonder the same thing... 😞

[jonathantneal]

@ashleynolan, are we able to add JUST the "eyeglass-module" keyword to make it compatible? If it requires more, do let me know the additional code you’ll need.

[jonathantneal]

Hey all, I’ll be closing this issue if we’re unable to get clearer instructions or an answer to my question by the 1st of January. Just trying to keep things moving along.

[ashleynolan]

@jonathantneal Sorry for not replying – should have kept on top of this.

From what I’ve done in the past, it involves adding the keyword and then having to add a couple of lines such as this. These point to the directory of the module, the name you want people to import the module as and the version of eyeglass supported.

[jonathantneal]

A PR for this could be made. I have not seen movement on this, though, so I am closing it.