A
A
Anubis2018-10-09 10:03:56
Node.js
Anubis, 2018-10-09 10:03:56

How to competently organize a boilerplate for web development?

There is a soupy set of webpack config files and linter settings that roams from one project to another with little or no change. I would like to move it to a separate project in order to solve the problem of code duplication and be able to centrally update these scripts and configs. At the project level, only the entry points and output files of webpack configs can vary. That is, we are talking about importing configs placed in a separate project and updating the entry and, possibly, output values. And about pulling up tslint.json and .stylelintrc from a common point.
I would like to receive advice on options for organizing and automating such a process.

Answer the question

In order to leave comments, you need to log in

2 answer(s)
A
Andrey Shubin, 2018-10-09
@Anubis

What about git submodule ?

A
Alexander Taratin, 2018-10-10
@Taraflex

https://github.com/Rich-Harris/degit - project generator based on git repositories.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question