Slimmer "common" template #723
kraenhansen
started this conversation in
Ideas
Replies: 1 comment
-
We'll have a template without any non-essential tools in the future. However, things like adding the choice of package manager puts more maintenance burden. We can't reasonably test so many combinations. So there won't be more customization options than that.
There's no default. Everything is a choice that you need to select before you generate the project. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The project's readme mentions:
While I see the value in making a certain choices for its users, I also recognize that it also comes with additional costs on the user to familiarize themselves with these additional tools. Adding to this, as a library developer (admittedly in the advanced end of the spectrum) I have my own preferences on these additional tools. I do however like the idea of initializing the native scaffolding for a React Native library from a CLI and this library has become the de-facto tool for this in the ecosystem, encoding the latest "best practice" around interfacing with React Native core APIs.
Long story short: I would love to be able to run the tool in a mode with less bloat (additional tools that are non-essential to building a React Native library) - and preferably this should be the default (with a choice add additional tools).
Here's a list of dependencies and tools that I would like to strip from the common template:
.github
.yarn
(ideally the choice of package manager should be based on the tool used to initialize the template)..editorconfig
.gitattributes
.nvmrc
.yarnrc.yml
lefthook.yml
@commitlint/config-conventional
@evilmartians/lefthook
@release-it/conventional-changelog
commitlint
release-it
turbo
Beta Was this translation helpful? Give feedback.
All reactions