# Set up a new Blendid project
mkdir <a new directory>
cd <that directory>
yarn init
# Add this PR's version of Blendid
yarn add ssh://git@github.com:vigetlabs/blendid.git#dependency-updates
yarn
# Verify that the basic functionality works
yarn run blendid init
yarn run blendid
# check live site in browser: html and js changes should trigger reload, stylesheet changes should hot update
# Verify that revving works
yarn run blendid build
# check static file in browser
yarn run blendid build
# verify that all references updated
and then in task-config.js change es2015 to env as explained at the top of this post.
Try on an exisiting project that uses data
Try on an exisiting Craft project
To revert your project to the latest version of Blendid run
yarn add blendid
To restore an older version of Blendid, run yarn add blendid@<version> or yarn add blendid@"<semver>". Or just discard the changes, delete the node_modules folder, and run yarn.
Changes
Where significant work was done that isn't clearly reflected in the diff, command history is included in the commit message.
Introduces breaking changes: in
task-config.js
'sjavascripts.babel.presets
,es2015
must be replaced withenv
. e.g.would become
What this PR does
npm audit
yarn upgrade --latest
What this PR doesn't do
Steps to test:
1. Dummy project
2. Existing projects
To use this update in an existing project, run
and then in task-config.js change
es2015
toenv
as explained at the top of this post.To revert your project to the latest version of Blendid run
To restore an older version of Blendid, run
yarn add blendid@<version>
oryarn add blendid@"<semver>"
. Or just discard the changes, delete the node_modules folder, and runyarn
.Changes
Where significant work was done that isn't clearly reflected in the diff, command history is included in the commit message.
Security-motivated updates
Warning resolution-motivated updates
General upkeep-motivated updates
Modernization-motivated updates: