I’ve added a SCSS function that, when passed a file path, will inject the file as a data URI. This
is super helpful since it ensures that the cursor images will always be available for the CSS. This
issue currently prevents the npm version of the library from being usable at all.
I've switched us from using `file-loader` to `url-loader`. This will automatically convert local URL
imports to data URIs, which means the framework no longer needs to load them from a remote URL.
#207
* refactor: add components directory
ref #166
* build: split nes.scss into nes.css and nes-core.css
and change npm scripts for build
ref #166
* docs(readme.md): add nes-core.css link
* docs: add components directory path
and minor modification of the document
* feat(storybook): Add backgrounds Storybook
I've added the Storybook backgrounds addon which allows users viewing the storybook to change the
background behind components, which will make it easier to see how the main NES.css theme looks in
various contexts.
* feat(storybook): Add backgrounds Storybook
I've added the Storybook backgrounds addon which allows users viewing the storybook to change the
background behind components, which will make it easier to see how the main NES.css theme looks in
various contexts.
We no longer need to build the entire framework to lint it, so I've removed the build step from the
pre-commit hook and replaced it with just stylelint.
I did a dumb. I changed the name of he script that updates the package headers before a release, but
I didn't tell `semantic-release-exec` that I'd changed it. 😬
I've add a script to handle automatically updating bot the CSS and SCSS headers with the relevant
information before publishing. This update is handled as part of `semantic-release`'s preparation
step.
I've moved the SCSS functions file into the `scripts` directory where I think it makes a bit more
sense. I've also abstracted most of the functionality from it so I can also use it in
`semantic-release`'s preparation step.
The `version` field in the `package.json` file doesn't serve any real purpose for us since
`semantic-release will handle adding and updating it automatically.
Hehehehe, this is really cool. I've removed the hardcoded version number from `nes.scss` and
replaced it with a custom function. This function does all sorts of cool stuff.
1. **Injects the framework version from `package.json`
This prevents us from having to inject the version number manually.
2. **Adds build info…**
The branch that the CSS was built from, when it was built, what version of Node was used… All of the useful information that we could possibly provide. If it’s built on CircleCI, it even includes the build number.
3. **…but not too much build info**
If the build is running against the `master` branch, we only inject the framework version. No need to bloat production builds with all the other junk. 😁
I've added hot reloading to Storybook. This means that during development, all we have to do is run
Storybook. As we make changes to the SCSS files, the changes will automatically be reflected in
Storybook. 😁
This removes `semantic-commitlint` from both the local build pipeline and the CI build pipeline. The
original value of `semantic-commitlint` was that it would handle linting only the relevant commits,
i.e. the commit range under review for a PR. However, the library doesn't seem to respect our
altered `commitlint` rules, so we'll be switching to an alternate strategy to handle linting of
specific ranges.
#13
Forcing contributors to use Commitizen to format their commit messages will make our lives much
simpler, especially once we've added `semantic-release`.
