Jon Koops
Jon Koops
@puggimer that is the console. check the network tab, click the failing request and then check the response, it should return some JSON which might contain additional details.
I agree with Prettier as a code formatter (also for the JavaScript code), as it eliminates a whole discussion point around code formatting. However, formatting is not linting. I think...
+1 for the new ESLint stuff, I like to stay in the same tooling ecosystem where possible.
Could you provide an example of the problem this fixes? I am quite curious how this would work in combination with `window.open()`.
@rolandjitsu got a proposal for running the tests on all versions of Node.js see #82
Not sure why, but semantic release decided to tag this with `3.0.0` which should have been `3.0.0-beta.1` and not the final tag, @rolandjitsu perhaps you can still pull this release?
Yeah, let's pull it and fix the configuration. I'll create a PR to fix it up if you can pull the NPM package.
Ah bummer, at least it was not tagged as the current release so it will not be installed automatically. We'll just have to use `3.0.1` as the first stable then.
Unfortunate, but that is what we'll be going for then. Such a shame that `semantic-release` is so aggressive. Perhaps we should find a way to configure it so we can...
Just wanted to chime in here that the reason a lot package maintainers (including myself) are increasingly choosing to adopt 'ESM only' as a strategy, is that we're already spread...