I have no doubt a thread here or elsewhere already covers my question but my searches haven’t satisfied me. I’m not trying to mend anything, just looking for best practice.
I’ve seen the material on Coursera from Goldsmiths, University of London, and edited and tested their meteor samples. I’ve also tried meteor create --examples. They generally require meteor npm install and then they run, which is nice. They all say patches are recommended, that newer versions of meteor are available and that the meteor npm audit is packed with High Severity vulnerabilities. My general impression is that in a production environment they ought to be updated.
My problem: every time I try --patch or update on meteor I hit a spiral of runaway dependency clashes, on all of these small demonstration systems. I’ve come back to the various bits of code several times to try to work out a stable process and I haven’t yet found the right path.
My question: is there a guide to updating code from, say, the last three years in a way that removes the audit warnings? Mostly because I’d quite like to use the examples as skeletons to learn on and they do seem to be intended for use that way. This strikes me as a beginner issue but I’m several turns round this cycle and I’m not making progress.
