Manuel Feller

I would also love to have a solution for that...

It seems that the API server was a victim of Herokus "shut down" of the free plan :( https://help.heroku.com/RSBRUH58/removal-of-heroku-free-product-plans-faq

/subscribe ;-) This could be helpful to give users some freedom how to set up their Ionic project (Cordova/Capacitor, Angular/React/VueJS, ...) and maybe also some other configuration topics. Let's gather...

Idea / suggestion to discuss: We add another field to the `context` object (that already contains `.projectId`, `.componentId` and `.group`) named `.userParams`. In there we pass a string that contains...

I would focus on the provisioning - since we could then allow customisation of cli-tools that set up things (e.g. using Angular or React in Ionic). And if I understand...

I will look a bit more into the way to define the params - the file was just a first thought, will check this a bit more in detail. Thanks...

Had the same concerns about the in general nice idea. I was thinking about some safelists for repo-domains that have to match, so you could even limit it to repos...

There may be, depending what you do: https://nodejs.org/tr/blog/uncategorized/10-lts-to-12-lts/#notable-changes And that is a quite long list of mostly small but sometimes behavioural changing or removing differences - not sure if each...

Regarding the `package-lock.json` we can not just say "do not push it". It has multiple purposes that we should not "throw away" - and also our company security team wants...

In the below image I show which build environments a node based project has to go through. Terminology: - local `.npmrc` = the one in the code repository - global...