I'm open to having an extended discussion about that. Although we should probably do that in the appropriate thread: https://lists.apache.org/thread.html/7f92561d382f143aaf49e083bbe215dcf95a3f4d8b6e3cbb6089a5f3@%3Cdev.cordova.apache.org%3E
Am Di., 11. Sep. 2018 um 13:14 Uhr schrieb Oliver Salzburg < [email protected]>: > I just wanted to voice my concern regarding package-locks on the list, > even though consensus was probably reached in the past already. > > From our experience, this is almost as bad as committing node_modules > into VCS. > I understand the idea behind them and I would agree with that idea, but > the implementation is horrible and suffers from many defects that > ultimately lead to developer frustration and hard-to-analyze bugs. > > Especially during development where you might switch between package > versions or link locally against development checkouts of modules, > package-lock files constantly get corrupted or operations even lead to > local development checkouts being replaced by cached npm modules, > because the lockfile had them marked as bundled. > And anytime something like that happens, you're left with having to > rebuild the lockfile from scratch, introducing exactly the changes you > didn't want in the first place. > > I understand that `npm ci` can have performance benefits during > installation of packages, but the underlying technologies are defective, > the time you save in CI will be spent by developers instead and you'll > likely roll back or have to deal with blocking npm issues for some time. > > That was the experience for us and I'd hate to see others make the same > mistake. If you go with it, I hope it works better for you and maybe I > will learn how it was all our own fault all along and we've just been > holding our iPhone the wrong way. :D > > Cheers > > > On 2018-09-11 08:14, Bryan Ellis wrote: > > Hey, how is everyone doing? > > > > As it is getting closer to the middle of September, I wanted to catch up > > and get a status update on how everyone is doing for the next major. > > > > Blow, I re-listed out the idea items for next major goals that were > > mentioned in a previous email. > > * > https://mail-archives.apache.org/mod_mbox/cordova-dev/201808.mbox/%3CCA+z8NA-tQJqqAFR0fJni7PzRG7LP3O0CbpqSytFHWYZefQb=-a...@mail.gmail.com%3E > > < > https://mail-archives.apache.org/mod_mbox/cordova-dev/201808.mbox/%3CCA+z8NA-tQJqqAFR0fJni7PzRG7LP3O0CbpqSytFHWYZefQb=-a...@mail.gmail.com%3E > >* > > > > I also want to point out that these items and others on next next major > > were added to the *"Apache Cordova: Next Release Planning and Tracking"* > > project board. *https://github.com/orgs/apache/projects/2 > > <https://github.com/orgs/apache/projects/2>* > > > > *Done* > > *====* > > * Remove usage of cordova-registry-mapper from tooling > > * Remove all old `--no-fetch` code > > * Refactor the cordova-fetch code to improve performance > > * Android: Adaptive Icons support > > * iOS: Fix for automatic provisioning > > * iOS: Improved Swift support > > * iOS: Fix CocoaPods Pathing Issue & Xcode 10 build ( > > https://github.com/apache/cordova-ios/pull/398) > > > > *In Progress* > > *===========* > > * iOS: CocoaPods Support Improvement ( > > https://github.com/apache/cordova-ios/issues/391) > > * Drop node 4 support from all repos > > * Drop committed node_modules from all platform repos > > * iOS: Bridge WebView plugin for WKWebView transition > > * Update the Hello Cordova starter to work with WKWebView & safe areas > > > > *To Do* > > *=====* > > * Commit package-lock.json in repos > > * iOS: Anything required for iOS 12 support > > * Android: Bring whitelist in-platform > > > > *Observation Items (Not an original task)* > > *=====* > > * ios-deploy: Xcode 10 & iOS 12 issue (ImportError: cannot import name > > _remove_dead_weakref) > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
