npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

stylelint-config-amp

v2.0.0

Published

stylelint config to enforce Accelerated Mobile Pages CSS restrictions

Downloads

27

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

tinovyatkintinovyatkin

Keywords

stylelintstylelint-configpostcssampmobileaccelerated-mobile-pagesvalidatorAccelerated Mobile PagesAMP HTMLvalidateamphtml

Readme

stylelint-config-amp

NPM version Build Status

The stylelint config to enforce CSS requirements of Accelerated Mobile Pages

AMP CSS requirements: https://amp.dev/documentation/guides-and-tutorials/develop/style_and_layout/style_pages/

This is stylelint config you may use either in authoring CSS for Accelerated Mobile Pages or for lint against requirements from Supported CSS for AMP and AMP HTML Specification. All allowed CSS code on that page must be inlined at single <style amp-custom> tag at a document <head>, so, you may use this config either from building tools during linting before inlining the CSS task or if your IDE support stylelint linting for inline rules.

Enforces all requirements that can be checked using current stylelint rules, including tag and classes names blacklist.

Note: the config is tested against AMP project homepage CSS that at the moment appears to violate it's own rules.

Installation

npm install stylelint-config-amp --save-dev

Usage

If you've installed stylelint-config-amp locally within your project, just set your stylelint config to:

{
  "extends": "stylelint-config-amp"
}

If you've globally installed stylelint-config-amp using the -g flag, then you'll need to use the absolute path to stylelint-config-amp in your config e.g.

{
  "extends": "/absolute/path/to/stylelint-config-amp"
}

Lint from a build script:

const config = require("stylelint-config-amp")
const { readFileSync } = require("fs")
const stylelint = require("stylelint")

function lint(filename, warningsCount) {
  return stylelint.lint({
    code: readFileSync(filename), "utf8"),
    config,
  })
  .then(result => {
    const { results:  [{ warnings }] } = result
    expect(warnings.length).toBe(warningsCount)
  })
}

Lint task for npm / yarn package.json:

"scripts": {
  "lint:amp-css": "stylelint --config=stylelint-config-amp src/stylesheets/amp/*.css"
},
"devDependencies": {
  "stylelint": "^10.0.0",
  "stylelint-config-amp": "^2.0.0"
}

Limitations

stylelint at the moment has no rules to check allowed declarations within @keyframes and I'm planing to submit pull request for such rule(s). We also don't check for maximum CSS size, nor for pseudo selectors used without tag names (it's prohibited at AMP) - I'm planing to submit such rules pull request to stylelint too.