These are chat archives for coala/coala-bears
package-lock.json, c.f. coala/coala-bears#2508
package.json, and maybe we should even just remove
package.jsonas some bear doesn’t adhere local package anyaway (like
ESLint) :smile: . Removing it means, we will have a hard time to know what npm dependency are required by coala-bears right?.
python3.6 -m pip install -r test-requirements.txt?
Nah, same problem.
With 18.04, Python doesn't come pre-installed, right?
I think some internal problem is there, reinstall OS if you can, please consider using it from the generic source, last time when I tried to do something creative it hit me hard.
pip installto see where it is installing things
PYTHONPATHto ensure that directory is seen by python
REQUIREMENTSfield. But for now, I rather like to have some package.json so users knowing npm can immediately install dependencies, so it just works. That's usually the faster and better understood way.
-gto be global
-gfor global package) it'll point to the directory where the installed executable is located
npxor make similar logic in Python based on both.
npmis just a weird package manager...