frets-styles-generator - npm Package Compare versions

Comparing version 0.1.4 to 0.1.5

CHANGELOG.md

		@@ -5,2 +5,7 @@ # Change Log

		<a name="0.1.5"></a>
		## [0.1.5](https://gitlab.com/FRETS/frets/compare/v0.1.4...v0.1.5) (2018-07-31)



		<a name="0.1.4"></a>
		@@ -7,0 +12,0 @@ ## [0.1.4](https://gitlab.com/FRETS/frets/compare/v0.1.2...v0.1.4) (2018-04-28)

package.json

		{
		"name": "frets-styles-generator",
		"version": "0.1.4",
		"version": "0.1.5",
		"description": "Tool that genreates a typescript class for FRETS based on a CSS file",
		@@ -5,0 +5,0 @@ "main": "build/main/index.js",

README.md

		# frets-styles-generator

		Genreates a typescript class from a given input css file.
		Genreates a typescript class from a given input css file.

		@@ -9,4 +9,4 @@ Uses postcss under the hood.

		Used in conjunction with FRETS and/or a hyperscript implementation like maquette. The current template outputs a ts file that expects maquette to be available, so you will need that in your project package.json as a dependency.
		Used in conjunction with FRETS and/or a hyperscript implementation. This particular template is specifically for the Maquette hyperscript implementation. Meaning it outputs a ts file that expects maquette to be available for import, so you will need 'maquette' in your project as a dependency.

		I find it especially useful if you point it at [BaseCSS](https://github.com/basscss/bassplate) or [tailwind](https://tailwindcss.com/).
		I find it especially useful for rapid prototyping if you point it at [BaseCSS](https://github.com/basscss/bassplate) or [tachyons](http://tachyons.io/) because then you have a chainable typescript method for every "atomic" css class.

build/main/build-style-type.d.ts

build/main/build-style-type.js

New alerts