patternlab-node
patternlab-node copied to clipboard
pattern-lab
The Node version of Pattern Lab
we could either continue to use `npm test` with a lot of complicated one-liner, or look into `lerna run test` to see if CI will respect each output cc @raphaelokon
As part of #811 and #840 we delivered the ability to exclude patterns in a UIKit. This works for both the writing of the files and for them showing up...
Implement https://github.com/pattern-lab/the-spec/issues/33 QUESTIONS: - [ ] determine if shared frontend needs to change PL NODE: - [ ] warn user if annotations file found - [ ] remove old method...
I am using Pattern Lab Node `v2.7.1` on `Linux`, with Node `v4.6.2`, using the `Grunt ` Edition. ##### Expected Behavior Especially for patterns in the `pages` category it should be...
hello. i care to use pattern lab to demo react components. amidst the huge amount of documentation floating around patternlab, the docs have not given me clarity on how I...
Closes https://github.com/pattern-lab/patternlab-node/issues/1500 ### Summary of changes: Migrating from expected Node version 16 to version 18, as Node 16 even already passed end of life state. This will result in a...
Closes https://github.com/pattern-lab/patternlab-node/issues/1501 Summary of changes: As [`pretty-quick`](https://www.npmjs.com/package/pretty-quick) is not being maintained any further, we're migrating to [`lint-staged`](https://www.npmjs.com/package/lint-staged).
As [`pretty-quick`](https://www.npmjs.com/package/pretty-quick) is not being maintained any further, we're migrating to [`lint-staged`](https://www.npmjs.com/package/lint-staged).
As Node 16 even also already got its end of life (https://endoflife.date/nodejs), we should migrate our codebase to Node 18.