2.11.0 - 2022-05-09
.jsfiles, like config files.
eas.json. It doesn't mean you need to use EAS or dev-client, you may still use Expo Go and Classic build, although EAS allows you to build for iOS without a Mac.
app.config.jswith some cool defaults and configs pattern.
babel.config.jswith configs for common libs.
./index.jsto support EAS.
A slightly opinionated central way to fastly create new projects with a single command.
Creating every single Typescript project environment is a real pain. Takes lots of minutes, sufferings and procrastinations to leave it functional and in the way I feel confortable to work with. We know how boring it really is.
There is a templates directory that contains all flavors boilerplates generated using the latest gev version.
npx gev <flavor> # To use the current directory as destination and package name. Directory emptiness will be checked. npx gev <flavor> <newPackageName> # To create a new directory and use it as the package name. Directory existence will be checked. npx gev -h # For help and all commands and options available.
Current available flavors are:
ts: Typescript project
expo: Expo project.
expo-pkg: React-Native/Expo components package. It's called expo because it will have a expo sandbox directory for testing your component.
All the flavors uses Typescript.
To supress the [email protected] possible npx confirmation message, you can use
npx -y gev.
Add Paypal donate button to the end of READMEs (or as a badge). Also funding.yml file.
Interactive menu to add other badges and the paypal button to the README.
Allow custom setups. It could be something like
npx gev -u githubUsername. This could really be a good way for people to have their own environment setup without too much work.
npm get and
set for local configs. Could store Github username, donation link, some package.json defaults and custom gev scripts to be used as default.
npx gev would open an interactive menu to choose the desired initializer or change user options.