edition-node-gulp | gulp wrapper around patternlab-node core | Frontend Framework library

by pattern-lab JavaScript Version: v2.0.0-alpha.3 License: MIT

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

kandi X-RAY | edition-node-gulp Summary

edition-node-gulp is a JavaScript library typically used in User Interface, Frontend Framework, Nodejs, Gulp applications. edition-node-gulp has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can install using 'npm i patternlab-eq-web' or download it from GitHub, npm.

The Gulp wrapper around Pattern Lab Node Core, the default PatternEngine, and supporting frontend assets.

Support

Quality

Security

License

Reuse

Support

edition-node-gulp has a low active ecosystem.

It has 287 star(s) with 116 fork(s). There are 23 watchers for this library.

It had no major release in the last 12 months.

There are 8 open issues and 65 have been closed. On average issues are closed in 53 days. There are 3 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of edition-node-gulp is v2.0.0-alpha.3

Quality

edition-node-gulp has 0 bugs and 0 code smells.

Security

edition-node-gulp has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

edition-node-gulp code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

edition-node-gulp is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

edition-node-gulp releases are available to install and integrate.

Deployable package is available in npm.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed edition-node-gulp and discovered the below as its top functions. This is intended to give you an instant insight into edition-node-gulp implemented functionality, and help decide if they suit your requirements.

Build the pattern
renders from config

Get all kandi verified functions for this library.

edition-node-gulp Key Features

No Key Features are available at this moment for edition-node-gulp.

edition-node-gulp Examples and Code Snippets

No Code Snippets are available at this moment for edition-node-gulp.

Community Discussions

Trending Discussions on edition-node-gulp

Adding selectize.js to patternlab.io implementation

Pattern Lab with second package.json

QUESTION

Adding selectize.js to patternlab.io implementation

Asked 2018-May-07 at 16:03

I have a patternlab implementation (edition-node-gulp). I'm trying to add selectize.js to it (https://github.com/selectize/selectize.js). When I add the indicated jquery function to the foot.mustache file, and check out the result, console indicates reference error: can't find variable $ (i.e. not recognizing jquery). When I add jquery.min.js to the head.mustache, above my selectize.js script tag, some of pattern lab's functionality stops working, some of it STARTS working, and I start getting different error messages (i.e. it now recognizes jquery). TypeError: $('#select-beast').selectize is not a function.

Here's head.mustache:

...

ANSWER

Answered 2018-Feb-16 at 16:54

Maintainer of Pattern Lab Node here.

In my opinion, your problem is your path.

Change it to

Because the way Pattern Lab outputs patterns, the base public/ directory is always two levels up. You'll notice the other files in that head pattern are going two levels up too.

public/

patterns/
- pattern-name/file
js/

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

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 edition-node-gulp

This edition comes pre-packaged with a couple simple gulp tasks. Extend them as needed. build patterns, copy assets, and construct ui. build patterns, copy assets, and construct ui, watch source files, and serve locally. logs Pattern Lab Node usage and help content. To interact further with Pattern Lab Node, such as to install plugins or starterkits, check out the rest of the gulpfile.js. You could also install the Pattern Lab Node Command Line Interface or learn more about the core API.

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: