Which supported boilerplate to choose for ES6/typescript?

Question

JavaScript

To start one project based on babylon.js (I considered three.js, but I still want something "more relevant" in terms of library code), I would not like to invent another "bicycle" and choose a boilerplate - a project template for a collector, without example project code (or which can be removed through a system clean up) and / or an imposed project structure (respectively, not a starter-kit, since there will be a hodgepodge of different modules).
Technology:

• ES6(babel?), typescript
  
• Scss or postscss (doesn't matter)
  
• Webpack/Gulp(watch/serve, build, autodocs(preferably, but can be neglected) & etc.) + eslint, + open configs directly in the project, not default settings
  
• npm (maybe yarn, but they seem to be compatible and in this case, in theory, it doesn’t matter)
  
• Not tied to a specific framework/js library
  

It is important that the project is not abandoned (when I searched, I often came across the fact that this or that project was last updated 1-2 years ago). It is also desirable that it contains basic documentation for all its components and configuration files, so as not to search.

Answer 1

In fact, this is exactly the case when you need to reinvent the wheel)
All you want is just a webpack config and a set of commands for launch, dev and production.
Accordingly, you need to install webpack and webpack-dev-server, show where to get files from, how to process (loaders are responsible for this), and where to collect them - do not be too lazy to study webpack, you can watch this screencast
Here is a simple example, I use this template to study typescript.
True, webpack 1 is already deprecated, but the difference in the config is not critical, so the screencast is still relevant.
Need ES6 along with typescript - add babel-loader
Need css preprocessor - add loader to this preprocessor
Linting needed - install eslint and Airbnb configs

Answer 2

In general, in the end, as I wrote earlier, since no solutions have already been proposed, I put together my own (webpack 2, devServer, eslint, bable, postcss, jade), in principle, in the future it will be possible to put it in the public domain.