From 3e43b23893294981e8c39d1050f2e96d47a9df01 Mon Sep 17 00:00:00 2001 From: Chris Hutchinson <1573022+chrishutchinson@users.noreply.github.com> Date: Sun, 20 Jun 2021 16:46:48 +0100 Subject: [PATCH] fix: update the Node.js version in package.json>engines (#98) --- README.md | 2 +- docs/code/Card.html | 2 +- docs/code/CardKit.html | 2 +- docs/code/CardKitDOM.html | 2 +- docs/code/CardKitServer.html | 2 +- docs/code/SVGToImage.html | 2 +- docs/code/cardkit.js.html | 2 +- docs/code/index.html | 10 +- docs/code/renderers_dom_SVGToImage.js.html | 2 +- docs/code/renderers_dom_dom.js.html | 2 +- docs/code/renderers_server_server.js.html | 2 +- docs/code/renderers_shared_Card.js.html | 2 +- package.json | 11 +- yarn.lock | 7933 ++++++++++++++++++++ 14 files changed, 7954 insertions(+), 22 deletions(-) create mode 100644 yarn.lock diff --git a/README.md b/README.md index a8f992c..c115ff9 100644 --- a/README.md +++ b/README.md @@ -18,7 +18,7 @@ Additionally, a base class allows you to create your own renderers. See more in CardKit requires a configuration object in order to render an image. Each renderer (CardKitDOM and CardKitServer) uses this configuration and converts it into an output. Below are simple implementations for CardKit depending on your use case. -In addition to these, you may also want to try the [CardKit Yeoman Generator](https://www.github.com/times/generator-cardkit), which can help you scaffold an entire project in just a few moments. It brings with it the latest version of CardKit, a recommended directory structure, and a build process that helps you get your CardKit project deployed. There is also a [JSFiddle](https://jsfiddle.net/chrishutchinson/16tLs2ta/) that you can fork and edit for quick in-browser testing without touching the command line. +In addition to these, you may also want to try the [CardKit Yeoman Generator](https://www.github.com/times/generator-cardkit), which can help you scaffold an entire project in just a few moments. It brings with it the latest version of CardKit, a recommended directory structure, and a build process that helps you get your CardKit project deployed. There is also a [JSFiddle](https://jsfiddle.net/chrishutchinson/16tLs2ta/) that you can fork and edit for quick in-browser testing without touching the command line. ### Previous versions diff --git a/docs/code/Card.html b/docs/code/Card.html index 111498a..e52c531 100644 --- a/docs/code/Card.html +++ b/docs/code/Card.html @@ -1155,7 +1155,7 @@
CardKitServer
: A server renderer, that allows you to take an instance of CardKit and render it into an image on a Node.js serverAdditionally, a base class allows you to create your own renderers. See more in the Custom Renderers section.
-For version 1, see the v1-master
branch
$ npm install cardkit --save
CardKit requires a configuration object in order to render an image. Each renderer (CardKitDOM and CardKitServer) uses this configuration and converts it into an output. Below are simple implementations for CardKit depending on your use case.
In addition to these, you may also want to try the CardKit Yeoman Generator, which can help you scaffold an entire project in just a few moments. It brings with it the latest version of CardKit, a recommended directory structure, and a build process that helps you get your CardKit project deployed. There is also a JSFiddle that you can fork and edit for quick in-browser testing without touching the command line.
+For version 1, see the v1-main
branch.
For version 2, see the v2-main
branch.
$ npm install -g yo generator-cardkit
$ yo cardkit
@@ -280,10 +282,8 @@ Custom Fonts
// ...
};
-Upgrading from v1.x to v2 should be a fairly straightforward process if you haven't made any major modifications to the v1.x user interface. Your configuration object from v1.x should be compatible with v2 with a few minor tweaks. Specific variations are available in the Wiki.
CardKit currently requires Node.js 8, which you can install using nvm
and running:
CardKit currently requires Node.js 14, which you can install using nvm
and running:
$ nvm use
To run a sample UI locally, run: $ npm start