Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why not published to NPM? #1

Open
phal0r opened this issue Jan 14, 2019 · 6 comments
Open

Why not published to NPM? #1

phal0r opened this issue Jan 14, 2019 · 6 comments

Comments

@phal0r
Copy link

phal0r commented Jan 14, 2019

Hi @joshdholtz ,

thanks for this nice project. May I ask why you did not publish it to npm?

@joshdholtz
Copy link
Owner

@phal0r Hey! This was more or less just something I did for myself as a proof of concept and a Hack & Tell (fun stressfree hackathon) one day. I was hoping that something like this would be built into Ionic one day so that I didn't have another thing to support myself 😉

@phal0r
Copy link
Author

phal0r commented Jan 15, 2019

I understand. So what is the point, that keeps you from making it more "official" (aka publishing it :P )
a) You don't have the time to maintain it
b) This is not well tested/finished

I have to 2 projects, where I want to have BETA/TEST/PROD versions without code duplication. Some configuration can be handled differently, but everything that is part of the cordova build system, would highly benefit from a tool like this. I feel that this could be build into the cordova lifecycle, so usage would be straightforward.

@joshdholtz
Copy link
Owner

@phal0r I love the questions here ❤️ I originally never published it to npm because its installable with npm install --save-dev https://github.com/joshdholtz/ionic-configurator.git and i was hoping something like this would get integrated into Ionic/Cordova natively but...

I'm just going to publish it today because yolo ✊ Stay tuned 😉

@phal0r
Copy link
Author

phal0r commented Jan 15, 2019

With Ionic 4 they include some support for different environments, so expecting to get a feature like this will probably take years, if it will be implemented at all.

Very cool! I am willing to help to set up some basic stuff... CI, Testing, Code Climate and so on. I can give feedback on how well it aligns with my projects.

I also promise to be the first to npm install it, right after you have published it :D

@phal0r
Copy link
Author

phal0r commented Jan 16, 2019

Another question: Does it make sense to publish it as cordova-configurator or cordova-multiapp-configurator (just thinking out loud)? Everything related to config.xml belongs to the cordova project. Ionic just builds upon it. It could be mentioned in the README, that it also supports Ionic and people don't get confused.

@joshdholtz
Copy link
Owner

I do like the idea of renaming it away from Ionic since it is 100% Cordova 🧐 I think I will do that and publish it so you can be the first downloader 🙌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants