Get help with testing, discuss unit testing strategies etc.
I'm trying to run the tutorial involved with the event recorder as seen here:
I do the npm install command and I'm getting errors that look like it is having issues finding Python. I have the latest version of Python installed on my machine at c:\Python38. The PATH environment variable points there and c:\Python38\Scripts. I'm attaching the log of what I see on the screen and the other log that it says to look at under AppData.
Let me know if there is anything more I need to do on my end.
This error appears because npm is trying to build the
node-saas module, which is regularly installed by downloading the pre-built binary.
It seems the
node-saas maintainers has removed the old version from the github.
Long story short, try upgrading the "node-sass-chokidar" dependency to the latest (package.json in the example folder):
Read the API documentation
That seems to have done it!
Unfortunately, the very next step is to execute: npm start-siesta
Here is the result:
Usage: npm <command>
where <command> is one of:
access, adduser, audit, bin, bugs, c, cache, ci, cit,
clean-install, clean-install-test, completion, config,
create, ddp, dedupe, deprecate, dist-tag, docs, doctor,
edit, explore, fund, get, help, help-search, hook, i, init,
install, install-ci-test, install-test, it, link, list, ln,
login, logout, ls, org, outdated, owner, pack, ping, prefix,
profile, prune, publish, rb, rebuild, repo, restart, root,
run, run-script, s, se, search, set, shrinkwrap, star,
stars, start, stop, t, team, test, token, tst, un,
uninstall, unpublish, unstar, up, update, v, version, view,
npm <command> -h quick help on <command>
npm -l display full usage info
npm help <term> search for help on <term>
npm help npm involved overview
Specify configs in the ini-formatted file:
or on the command line via: npm <command> --key value
Config info can be viewed via: npm help config
firstname.lastname@example.org C:\Program Files\nodejs\node_modules\npm
And if any Bryntum folks are reading this, the path to the example is incorrect.