Raphael Schweikert

> why not using a separate tsconfig I’m a tidy person. It bothers me. It’s bad enough that so many tools, including jest, are adamant about polluting my project dir...

That makes sense, thanks!

This is more about npm than it is about docker. NPM 6 introduced reproducible installs using `npm ci`, which installs from `package-lock.json`. Installing using `npm i[nstall]`, in contrast, installs from...

I got a notification from Travis CI that the build failed: ``` 4.35s$ npm ci npm WARN prepare removing existing node_modules/ before installation npm ERR! nice-try not accessible from get-audio-duration:cross-spawn...

Now that part of the build works but it fails at eslint, see https://travis-ci.com/github/sabberworm/nodetube/jobs/323466818. I’m pretty sure that has nothing to do with my change, however…

Whenever you install something via npm, the lockfile should automatically be updated.

I don’t know why the previous lockfile was invalid. Could be the result of a merge where two branches changed something in `package.json` and git was able to merge the...

I don’t think `REQUEST_ITEM`s need to be allowed to come before the `URL` but it sure would be great if the `--`-prefixed options would be allowed everywhere. Specifically, I often...

FWIW, versions 0.38.0 through 0.45.0 were all working fine for me when bundling with parcel. Starting with 0.46.0, the build fails again, due to the way parcel shims the `process`...

> I've done some poking around, and it looks like the tree_mariadb.py file has `def get_tree_info(request):` > > but all of the other tree_.py files have > > `def get_tree_info(request,...