Patterns is a toolkit that enables designers to build rich interactive prototypes without the need for writing any JavaScript. All functionality is triggered by classes and other attributes in the HTML, without abusing the HTML as a programming language. Accessibility, SEO and well structured HTML are core values of Patterns.
See the Changelog at GitHub.
Patterns aims to support at least the two latest major versions of all popular browsers:
Other browser version may work too, but are not actively tested against.
Make sure, you have these requirements installed:
- Node.js ( https://nodejs.org/en/ )
- yarn ( https://yarnpkg.com/ )
- make
- git
On OSX you need gnu-tar
instead of tar (GNU tar supports the --transform
option).
Please install it with e.g. brew install gnu-tar
.
The following commands will generate a bundle.min.js
file in the dist
directory
which contains Patterns and all its dependencies:
git clone git://github.com/Patternslib/Patterns.git
cd Patterns
make
Alternatively, you can download a bundle at patternslib.com.
The individual patterns are located in their own folders in ./src/pat/
.
Each pattern folder contains some or all of the following files:
To generate CSS files from the pattern's included Sass files, type make all_css
and the css files will be generated in the same location as the Sass files.
You'll need to have a Sass compiler installed.
To demo the patterns, simply type make serve
to install the necessary
dependencies and to start a simple Node.js HTTP server.
You can then visit http://localhost:4001 to see a site with demos.
Alternatively, patterns can also be demoed through the Patternslib.com website, which is open-source. The code and setup instructions are here.
To develop on Patterns, clone the repository and set it's push-url to your fork:
git remote set-url --push origin <url_to_your_fork>
Create a branch for the feature/bug you are working on:
git checkout -b <feature>
For inclusion use either a GitHub pull request or create a ticket with a url to your external repository.
Please read our contribution notes and read our code style guide.
The simplest way to run the tests are to use make:
make check
This will install all required npm and bower packages and run the tests.
Eventually add to tests:
import "core-js/stable";
import "regenerator-runtime/runtime";
Then:
node --inspect-brk node_modules/.bin/jest --runInBand ./src/pat/tooltip/tooltip.test.js
Connect in chrome via:
chrome://inspect
You can pass Jest any parameter it accepts, like -t TESTPATTERN
::
node --inspect-brk node_modules/.bin/jest --runInBand ./src/pat/tooltip/tooltip.test.js -t will.be.closed.when
To facilitate debugging you can change the default log level through the URL query string by adding loglevel
options.
http://www.example.com/?loglevel=DEBUG
changes the default log level to DEBUG
.http://www.example.com/?loglevel-inject=DEBUG
changes the log level for just the inject pattern to DEBUG
.http://www.example.com/?loglevel=ERROR&loglevel-inject=INFO
changes the standard log level error, but enables messages at the INFO
level for the inject pattern.https://survivejs.com/webpack/optimizing/build-analysis/ https://formidable.com/blog/2018/finding-webpack-duplicates-with-inspectpack-plugin/
Build the stats.json file:
yarn build:stats
Check dependency tree and why which package was included: https://www.npmjs.com/package/whybundled
whybundled stats.json
Visualize dependency tree and analyze bundle size: https://www.npmjs.com/package/webpack-bundle-analyzer
webpack-bundle-analyzer stats.json