Raphael von der Grün

@erisu I know you did some work on this. Unfortunately the PRs/commits didn't reference this issue. I guess this is not yet done in all repos. How do we want...

Copy of my comment from https://github.com/apache/cordova-cli/issues/529 for better visibility: I think not having to rely on the presence of the `www` folder is a reasonable request. But before that change...

It is worth to mention that `cordova-serve` does not yet depend on `cordova-common`. If we want to keep it that way, we could evaluate if it really needs to search...

Regardless of where we put it, one possibility for the new algorithm could be: ```js const fs = require('fs'); const path = require('path'); const pkgUpSync = require('pkg-up').sync; module.exports = function...

Good point about the electron case, @erisu. So that means we need a different process after all :disappointed: Random ideas: - look at the content of the files - (re-)introduce...

I've added a dependency graph to make it easier to determine the correct order of doing this.

Should anyone want to tackle this for some repo, here's some of the "tools" I've been using: List of Q instance methods: ``` passByCopy join tap thenResolve thenReject isPending isFulfilled...

Too bad nobody wrote an automated code transformation based on [jscodeshift](https://github.com/facebook/jscodeshift) for migrating from Q to native Promises.

I wrote an ESLint config that should highlight all instances of Q-API usage: ```js const qInstanceMethodsConfig = ` allResolved allSettled del delay denodeify dispatch done fail fapply fbind fcall fin...

> because both files begin with > > ``` > cordova.define("cordova-plugin-globalization.GlobalizationProxy", function(require, exports, module) { > ``` Is that module name correct? It does not match the error message you...