# gatsby-theme-klassy

> klassy adds the basis for styling your Gatsby projects with [PostCSS](https://postcss.org).

Latest version **0.0.3** (published 2019-05-30) · Apache-2.0 license · 0 weekly downloads

## Install

```sh
npm install gatsby-theme-klassy
pnpm add gatsby-theme-klassy
yarn add gatsby-theme-klassy
bun add gatsby-theme-klassy
```

## Health

**Score 15/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support; pre 1.0.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 0.0.3 |
| Published | 2019-05-30 |
| First published | 2019-03-16 |
| Weekly downloads | 0 |
| License | Apache-2.0 |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 2 |
| Unpacked size | 3.4 KB |
| Known vulnerabilities | 0 |
| Install scripts | no |
| Author | Henrique Cavalieri |
| Maintainers | hcavalieri |
| Keywords | gatsby, gatsby-theme, gatsby-style-theme, gatsby-themes, postcss |

## Links

- npm: https://www.npmjs.com/package/gatsby-theme-klassy
- npm.io page: https://npm.io/package/gatsby-theme-klassy

## Dependencies (2)

- [postcss-preset-env](https://npm.io/package/postcss-preset-env.md) ^6.6.0
- [gatsby-plugin-postcss](https://npm.io/package/gatsby-plugin-postcss.md) ^2.0.7

## Recent versions

- 0.0.3 (latest) — 2019-05-30
- 0.0.2 — 2019-03-16
- 0.0.1 — 2019-03-16

## README

# gatsby-theme-klassy

klassy adds the basis for styling your Gatsby projects with [PostCSS](https://postcss.org).

## Usage

```shell
npm i gatsby-theme-klassy
# or
yarn add gatsby-theme-klassy
```

All the available options are listed in the example below:

```js
// in your gatsby-config.js
module.exports = {
  __experimentalThemes: [
    {
      resolve: 'gatsby-theme-klassy',
      // options: {
      //   useSharp: false, // defaults to false
      //   useNetlify: true, // defaults to false
      //   useSitemap: true, // defaults to false
      //   siteUrl: 'https://gatsbyjs.org', // necessary for `useSitemap`
      // }
    }
  ]
  // ...
}
```

## Note on dependencies

Many npm packages aren't transparent about why and how they add dependencies to your projects, and that's part of the reason why our `node_modules` folder is so bloated... if your dependency graph concerns you, be sure to read below.

This theme includes the following packages as dependencies, meaning you'll download all of them when using it:

```json
{
  "dependencies": {
    "@babel/plugin-transform-typescript": "^7.1.0",
    "@kompanion/utils": "*",
    "@types/react-helmet": "^5.0.8",
    "gatsby-plugin-page-creator": "^2.0.10",
    "gatsby-plugin-react-helmet": "^3.0.7",
    "gatsby-plugin-sharp": "^2.0.28",
    "gatsby-plugin-sitemap": "^2.0.9",
    "gatsby-plugin-typescript": "^2.0.9",
    "gatsby-transformer-sharp": "^2.1.17",
    "gatsby-plugin-netlify": "^2.0.11",
    "react-helmet": "^5.2.0",
    "typescript": "^3.3.0"
  },
}
```

This is an intended behavior to simplify development as, by doing so, you **need only install `gatsby-theme-koncrete` and not have to worry about the other packages**, freeing space and complexity in your `package.json`.

Also, having the package doesn't mean you have to use it: if you don't turn them on in the theme's properties, Gatsby won't do anything about it and your runtime won't be affected 😉

## TODO

- set-up prettier and eslint (or standardJS)
- **documentation**
- Investigate if there's a way to set-up `prettier` and `tslint`/`eslint` to run on sites
  - This might be better off with starters as configuration is highly personal and might incurr in headaches for users

---
_Source: https://npm.io/package/gatsby-theme-klassy · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._