Reinis Ivanovs

Generating an ESLint config that would extend the XO config would make editor integrations work out-of-the-box for all the editors that support it; instead, now XO-specific [editor extensions][0] are required....

@TrySound I mentioned this caveat about needing to publish from the build directory. [This is][this] what MUI does; it copies `package.json` to the build directory. [this]: https://github.com/mui-org/material-ui/blob/master/scripts/copy-files.js#L64-L82

@schmod Thanks for the informative link; supporting tree shaking better is an additional reason to avoid bundling the library. Publishing from the build directory would still be desirable, though, because...

CoffeeScript largely lacks relevance these days, so it's probably not useful to invest resources in.

Sorry, my comment was not intended to be inflammatory, but providing TypeScript type definitions is a significant convenience for library consumers, as it integrates with the code intelligence features in...

`LEIN_USE_BOOTCLASSPATH=no` works but should at the very least be mentioned in the readme.

Applying the env workaround from the console was simple, but it was less simple to figure out how to get the VS Code remote extension to work; in the end,...

This boilerplate is generally out of date, so I'd suggest avoiding it; for example, the current best practices are using `@babel/preset-typescript` instead of `tsc` to downlevel-compile, and using `typescript-eslint` instead...

If `cy.intercept()` is used for mocking, for example, assets and not just API calls, it can flood the command log and make it difficult to overview, so a feature to...

It reached stage 4 and is part of ES2018.