Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

plexiform

Package Overview
Dependencies
Maintainers
2
Versions
33
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

plexiform - npm Package Compare versions

Comparing version 3.3.0 to 3.3.1

0

builds/_boilerplate.js

@@ -0,0 +0,0 @@ // jshint esversion: 6

@@ -0,0 +0,0 @@ // jshint esversion: 6

@@ -0,0 +0,0 @@ {

@@ -0,0 +0,0 @@ /* jshint esversion: 6 */

@@ -0,0 +0,0 @@ /* jshint esversion: 6 */

25

index.js

@@ -31,3 +31,3 @@ #!/usr/bin/env node

name: "Plexiform",
version: "3.3.0",
version: "3.3.1",
author: "Raith"

@@ -64,3 +64,3 @@ };

// parameterised options
var build_name = argv.options.build || null;
var build_name = argv.options.build || "*";
var spec_name = argv.options.spec || null;

@@ -100,6 +100,6 @@ var output_folder = argv.options.output || null;

plexiform init [--force]
plexiform init [--force] [--build <build_name>] [--spec <spec_name>] [--output <output_folder>]
plexiform init [--force] [--spec <spec_name>] [--build <build_name>] [--output <output_folder>]
plexiform build [--save]
plexiform build --build <build_name> [--spec <spec_name>] [--output <output_folder>] [--save]
plexiform build --spec <spec_name> [--build <build_name>] [--output <output_folder>] [--save]

@@ -121,11 +121,5 @@ plexiform gallery list

"plexiform build" without the build_name being specified will require the ${plexiformconfigname} file in the CURRENT WORKING DIRECTORY.
In this case, the specified build_name, spec_name, and output_folder are as-per the parameters explained hereafter, including that they should be relative to the cwd, or elsewhere in the 'module paths' (where they can be require'd).
"plexiform build" without the spec_name being specified will require the ${plexiformconfigname} file in the CURRENT WORKING DIRECTORY.
In this case, the specified spec_name, build_name, and output_folder are as-per the parameters explained hereafter, including that they should be relative to the cwd, or elsewhere in the 'module paths' (where they can be require'd).
<build_name>
This should refer to a file with extension ".js" in the CWD or modules path (for require).
It is a node module which exports a method named "build" with signature (spec, utils) => void which will perform your build.
It may also export a method named "process" with signature (input) => specification_object which will process a non-json specification file.
If "*" is specified then all modules named "plexiform-build-*" are required from the current node_modules path.
<spec_name>

@@ -139,2 +133,9 @@ This should refer to a "json", "md", or other file, relative to the CWD.

<build_name>
This should refer to a file with extension ".js" in the CWD or modules path (for require).
It is a node module which exports a method named "build" with signature (spec, utils) => void which will perform your build.
It may also export a method named "process" with signature (input) => specification_object which will process a non-json specification file.
If no <build_name> is specified then "*" is assumed, unless it is looked up from ${plexiformconfigname}
If "*" is specified then all modules named "plexiform-build-*" are required from the current node_modules path.
<output_folder>

@@ -141,0 +142,0 @@ The folder into which files are generated.

{
"name": "plexiform",
"version": "3.3.0",
"version": "3.3.1",
"description": "A very simple template-driven generator.",

@@ -5,0 +5,0 @@ "main": "index.js",

# Plexiform
> **v3.3.0**
> **v3.3.1**

@@ -5,0 +5,0 @@ | In this document |

@@ -0,0 +0,0 @@ {

@@ -36,3 +36,4 @@ # Plexiform

| 2018-01-09 | v3.3.0 | Raith | Multi-build support. Specify --build * to process with ALL modules named "plexiform-build-*" |
| 2018-01-10 | v3.3.1 | Raith | spec_name now higher priority than build_name which defaults to "*" |
---

Sorry, the diff of this file is not supported yet

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc