pattern-lab | based project to supply Sass components | Style Language library

by comicrelief CSS Version: v7.68.0 License: GPL-2.0

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | pattern-lab Summary

pattern-lab is a CSS library typically used in User Interface, Style Language applications. pattern-lab has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has low support. You can download it from GitHub.

A Node-based project to supply Sass components and a styleguide generator.

Support

Quality

Security

License

Reuse

Support

pattern-lab has a low active ecosystem.

It has 17 star(s) with 1 fork(s). There are 19 watchers for this library.

It had no major release in the last 12 months.

There are 11 open issues and 411 have been closed. On average issues are closed in 8 days. There are 26 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of pattern-lab is v7.68.0

Quality

pattern-lab has no bugs reported.

Security

pattern-lab has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

pattern-lab is licensed under the GPL-2.0 License. This license is Strong Copyleft.

Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

Reuse

pattern-lab releases are available to install and integrate.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of pattern-lab

Get all kandi verified functions for this library.

pattern-lab Key Features

No Key Features are available at this moment for pattern-lab.

pattern-lab Examples and Code Snippets

No Code Snippets are available at this moment for pattern-lab.

Community Discussions

Trending Discussions on pattern-lab

Problem installing Pattern Lab 3 plus Twig

Pattern Lab with second package.json

QUESTION

Problem installing Pattern Lab 3 plus Twig

Asked 2020-May-01 at 14:00

I'm having some trouble with Pattern Lab 3 plus Twig.

Following the instructions at https://patternlab.io/docs/installation.html:

I install with: npm create pattern-lab.
I choose Twig (PHP) as the templating language.
I choose Twig (PHP) demo patterns (full demo website and patterns) as the the initial patterns

I do see the note The PHP version of Pattern Lab is being deprecated in favor of a new unified Pattern Lab core. The PHP docs for this topic can be viewed here.. Clicking on the link just takes me to installtion page for PHP edition of PL v.2. Not helpful. So I press on to https://patternlab.io/docs/generating-pattern-lab.html.

Next I'm supposed to run php core/console --watch. There is no core sub-directory. Things are not looking promising.

I remove my PL installation and try again with handlebars templating. With one exception, all is good. The exception: I wanted twig templates.

Ideas?

...

ANSWER

Answered 2020-May-01 at 14:00

Indeed, the PatternLab website you saw around the time you posted this still reflected the 2.x/3.x days. Work is being done to get the legacy out and the current state in.

Last month, I contributed to this package: @pattern-lab/engine-twig. This engine is a pure Javascript based twig engine which prevents the need for PHP. It uses the Twing library under the hood (since v5.8.0). There are still things to iron out, but I welcome you to try it. Please file bugs here:

https://github.com/pattern-lab/patternlab-node/issues

Source https://stackoverflow.com/questions/60442580

QUESTION

Pattern Lab with second package.json

Asked 2017-Dec-21 at 22:48

I have a Pattern Lab edition-node-gulp set up and would like to use NPM to manage UI dependencies, like jQuery, D3 and others. Pattern Lab is set up so that development happens in a 'Source' folder, which is complied and moved to a 'Public' folder. The root of the Public folder becomes the root of the application when served.

Currently, I include assets like jQuery and others manually. I think it would be great to manage dependencies like jQuery right in the package.json file used to run all of Pattern Lab Node, but the node_modules folder exists outside of Public, so I can not reference it in the live application.

So far, it seems that I have two options:

Continue as is, and forget package management for these assets.
Create a second package.json inside Public with jQuery and others, which seems sloppy.

Is creating a second package.json so bad? Am I failing to consider some other option?

...

ANSWER

Answered 2017-Dec-21 at 22:48

Creating a second package.json is not that bad (when you know what and how you are doing of course). However in your particular case it is not the best scenario because there are way better options.

What is the problem? Adding the assets to the build output. So, what you can do:

install the assets via npm install and save them in the original package.json
adapt gulpfile.js to copy the files in the output directory.

If the second step step is too hacky / problematic it could be also replaced with simple package.json scripts change (add build script):

Source https://stackoverflow.com/questions/47933648

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install pattern-lab

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: