Quantcast
Channel: Ionic Forum - Latest topics
Viewing all articles
Browse latest Browse all 70748

Need directions on updating packages (ionic v3 + native + npm etc)

$
0
0

@bozden wrote:

I’m fairly new in node/cordova/angular/ionic etc… I build my first app for android and released as a closed beta and collected a couple of problems. I found some of the problems are caused by bugs in native code etc.

I use Genymotion, VS Code and every possible helper plugin, also on device executions.

During this course I had to update, remove all packages, re-build all, etc. and it got worse. Now I even cannot build a stable release…

My question is NOT related to a specific bug. I rather want to know how you guys/gals manage it. I had a fixation in upgrading all software continuously, but I see that cannot be the case here.

This is what I do and what I want to know:

  1. Check Android Studio and update. If needed check the environment variables (paths etc) also.

  2. I check https://github.com/ionic-team/ionic/blob/master/CHANGELOG.md and see what is the latest supported packages and fix those versions in the package.json file and update.
    Question: This changelog is updated rather slow, e.g. @angular/* packages are now at 5.1.3 but the changelog states 5.0.0. Can I upgrade these and when?

  3. I upgrade node.js from time to time, but keep multiple copies with nvm-windows utility.
    Question: Is it safe to use the latest stable node.js in ionic development?

  4. I use “npm outdated -g” and/or “npm-check-updates -g” utility and I do upgrade (except typescript).
    Question: Is this safe?

  5. I use “npm outdated” and/or “npm-check-updates” utility for local packages and I do upgrade all-not-version-fixed packages.
    Question: Is this safe?

  6. I use “cordova-check-plugins” utility for local cordova plugin packages and I do upgrade all packages.
    Question: Is this safe?

  7. If anything is messed-up, I cleanup and rebuild.
    Delete node_modules, platforms, plugins and www directories and rebuild everything with:

  • npm install --save --no-optional
  • ionic cordova prepare

Sometimes I use:

  • remove/add android platform
  • remove/add cordova plugins + reinstall @ionic-native packages latest versions
    I wrote a batch file for this and I keep it updated for a specific project…
    Question: Do you frequently use this or am I lost?
  1. If I’m totally lost I remove everything and rebuild the development environment from scratch (node, npm, npm caches etc - I did this 3 or 4 times in the last 2-3 months with this project).
    Question: Do you ever need to do this?

A feature may work in one (older) cordova-android but another feature needs a later one…

I’m lost in github’s open issues, closed issues, re-opened issues, changelogs etc. This is a simple app after all and ionic development supposed to be easy, isn’t it?

As you can see I’m totally frustrated and confused… There must be an easier and more solid way.

Please share your knowledge on “never do”, “must do”, “should do” and "can do"s in package version management.

I think many novices hit these walls…

Thanks in advance…

Posts: 1

Participants: 1

Read full topic


Viewing all articles
Browse latest Browse all 70748

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>