Federico Miras

We should log more readable errors when cache-micro: - can't write - can't read - can't open a connection - can't close database

We must test all the mongo or in-memory conditional sentences and reach 100% of coverage

We already support Mongo for data horizontal cache. Redis is better when is about volatile in-memory data.

Only commit package.json instead of all files

1

Is it viable to just add `package.json` after bumping version instead making a `git add -A`? I can send the PR myself https://github.com/zeit/release/blob/0b421e071e9bcbf66bbfe4702a0743145260ac1e/lib/bump.js#L112 cc @leo

Support usage of custom next.js server

1

We should support usage of custom next.js server with next-pkg dist script, maybe reading `package.json` start script so developers don't need to use pkg manually.

Windows need binary file on same path as .next

1

When using next-pkg on windows, dist file requires to be on same path as .next compiled sources. It should be independent of it's location and also file self-dependent

When installing `next-pkg` and running the `npm run dist` which we suggest from the `README.md` isn't going to work unless the user runs `next build` we should warn/ask to build...

Next-Pkg cli package should accepto pkg cli arguments such as `--target` or `--output` using the exec exported function: ```javascript await exec([ 'app.js', '--target', 'host', '--output', 'app.exe' ]) // do something...

Next-Pkg should support package.json pkg configuration as same as pkg does (for example, with assets and scripts properties). ```json "pkg": { "scripts": "build/**/*.js", "assets": "views/**/*" } ```

Should we show a refresh button on Linker Dapp error? cc @nicosantangelo