https://stackoverflow.com/questions/47456617/why-did-npm-deleted-empty-folder-when-published-package-to-npm-registry

The only solution I can think of is:

Have a prebuild script that will find empty dirs in the semitemplates and write them in a .json, like

emptyDirs.json

{
  "expo": [
    "src/components/common",
    "src/components/contexts",
  ] 
}

etc. Store it maybe on data/. On applySemitemplates(), those would be created for the current flavor.

This apply isn't require on dev env, as the empty dirs exists on local semitemplate dir.

th3rdwave/react-native-safe-area-context#125

Less painful to create new flavors. Each flavor exports as default its function.

Could even, instead of having a array of existing flavors, have a on the run flavor's dir files read.

• screens/.
• main/ for consts.ts, index.tsx... in the root it gets quickly polluted.
• components/
• stores/ | classes/ for mobx? Edit ~6 months later, I no longer use mobx as it makes code less predictable and readable. Using React Context now.

Solution:

Have a array of items before the writes, and on error clean all but them.

it was added on rn flavor.

Quick soon todo/free thinking:

1. Check gev version and recall with @latest if not latest already (as npx will unfortunatelly use old versions if available in cache) done in 2.2.0

2. Interactive menu to choose the flavor, project name, dest path (maybe)

   • Called with just npx gev? This would require removing ts as default flavor.
   • Would npx gev ts also have a interactive menu? Or only npx gev ts -i would do it?

3. Multiple common dependencies to be additionally installed. They could all be in the root, but could also be categorized. As my common deps wouldn't be the same as everyone else's and having all the deps showing there would be a huge pollution, there could be the common ones (like most popular ones), but also the user saved ones. This could also be set in the future user personal flavor. The user could also write the deps' names to add / find them (this is similar to the idea I sent to the vscode/typescript team on a seasonal form, and then to an extension idea I already had*). The main flavor (template) could still be the ts, but with the spices (those additional and specific configs). There could be an option in the interactive menu like Use personal spice and the user saved spices would show there. But maybe both concepts wouldn't be clear to separate one from the other. Anyway, the user flavors/spices would be accessible via local storage or github repo / gist. Just the username could be entered, and it would look for public repos (or private ones if logged) and the desired spice could then be selected, if multiple ones are present.

There could be a user@ts template, but also a user@ts#expo. Maybe, just using user@ts would ask for the spice. user@ts# would use the default one the user has. Maybe it's getting more complex than it should.

* -> 4) I could do a gev extension for the VsCode. Instead of calling it by the terminal, it would also be possible to use it via GUI in vscode. Not really hard to do but as it certainly would translate to a cli call, I need the cli structure to be in its final form. It's all coming together!

Quite a pain to fix/improve a script in multiple projects and to ensure they are using the latest one.

It would replace existing scripts and add new ones to the end (maybe after a new line). It can have an interactive menu to update it, but perhaps just printing the latest scripts will do it.

Something that worked for tsconfig would also do it.

There could be a unified way to set the common scripts with a function in the program instead of defining each one individually.

E.g.

# EditorConfig helps developers define and maintain consistent
# coding styles between different editors and IDEs
# editorconfig.org

root = true

[*]

# change these settings to your own preference
indent_style = space
indent_size = 2

# we recommend you to keep these unchanged
end_of_line = lf
charset = utf-8
trim_trailing_whitespace = true
insert_final_newline = true

[*.md]
trim_trailing_whitespace = false

(https://github.com/callstack/react-native-paper/blob/main/.editorconfig).

Read other projects' .editorconfig to make the best one.

Example, rn flavor sets by default the pkg json version as 0.0.1, but the CHANGELOG had the initial version as 0.1.0. A SSOT would suit better.

tj/commander.js#1559

cli flavor = ts flavor + additional packages: commander, chalk, ora.

Will have an index.ts with basic commander code.

Do it on next project, check if our app.config.js hasn't something important that app.json has

And also, remove SafeAreaView from App.