Recent update breaks the build/old flow

[simonebogni]

Hi, I've started using this boilerplate for a Zendesk project. It looks really promising and I really wanted to integrate it in our app development process. However, I've noticed that the update from 3 days ago introduced significant changes. As a result, the way to create a regular app (e.g. in the ticket sidebar) is different and the docs and scripts have not been updated. Unfortunately this makes the boilerplate unusable at the moment - at least from what I've seen.

The repository is also using 3 different package managers (npm, yarn and pnpm), but the scripts expect you to run yarn. Package-lock.json (for npm) is not updated, compared to the other 2 files. I suggest one of the following options:

• give the option to developers to choose what tool they want. That means keeping all the lock files updated and either updating the script to accept the name of the package manager as a parameter, or have a section in the docs that explain how and where to make the change in the scripts
• stick to only yarn

I imagine it's still a work in progress, but please consider doing these changes on feature branches and not on the main branch. In the same major version, changes should be backward compatible. The lack of releases or tags on this repo makes it also very hard to clone an old stable version. Thank you :)