Backstop 2.8.x include breaking changes
See original GitHub issueLooks like the 2.8.x release of BackstopJS includes breaking changes because of a dependency (https://github.com/OnetapInc/chromy) which require Node.js 8 whereas previously using BackstopJS didn’t require such a new version of Node.JS.
I think this change should be released as 3.x so that it follow semver practice and doesn’t break existing builds.
FYI the error we are now getting is:
/c/dev/project/node_modules/chromy/src/index.js:73
async start (startingUrl = null) {
SyntaxError: Unexpected identifier
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
backstopjs
The BackstopJS workflow · backstop init : Set up a new BackstopJS instance -- specify URLs, cookies, screen sizes, DOM selectors, interactions ...
Read more >OpenSSH: Release Notes
OpenSSH is a 100% complete SSH protocol 2.0 implementation and includes sftp client and server support. Once again, we would like to thank...
Read more >Overrunning and Backstopping Clutches
This spragtype design overrunning clutch generally consists of an inner race, an outer race, a set of sprags, a sprag retainer, energizing springs,...
Read more >7 Brake and backstop
This brake control has a wear-free, electronic switch which prevents, in particular, contact-breaking sparks when switching off the brake which could lead to ......
Read more >pipelines/CHANGELOG.md at master · kubeflow ...
XGBoost demo - change quota calculation #3093 (SinaChavoshi); [Doc] Call out quota requirement in XGBoost sample #3092 (numerology); SDK - Fixed the broken...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Version 6.10.0. Looking at the PR on chromy this issue should be fixed quite soon I hope.
Thanks very much for your comments!