From e7afc585b287945ba49f8fc29e3e810e89b55474 Mon Sep 17 00:00:00 2001 From: Lauri Ojansivu Date: Wed, 20 Sep 2023 11:26:24 +0300 Subject: [PATCH] Updated Debugging (markdown) --- Debugging.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/Debugging.md b/Debugging.md index 5e6f336..d76a14b 100644 --- a/Debugging.md +++ b/Debugging.md @@ -9,9 +9,8 @@ To fix it: ``` meteor run --exclude-archs web.browser.legacy,web.cordova --port 4000 --extra-packages bundle-visualizer --production 2>&1 | tee ../log.txt ``` -3. Make dependencies smaller. For example, use only required files, and do not include all dependencies: https://github.com/wekan/wekan/commit/23e5e1e3bd081699ce39ce5887db7e612616014d -4. Use Browserstack.com to see errors at browser / inspect / console, or use iOS or other device emulators, to see error messages. Those error messages have file where error happened, and line number, like `something.js:301` . From there, scroll up a little, look at what function or what package dependency it is where it happened. If possible, try to move that package serverside, like at step 1. Or alternatively, look is it possible to remove or change to some other compatible dependency. - +3. Make dependencies smaller. For example, use only required files, and do not include all dependencies: https://github.com/wekan/wekan/commit/23e5e1e3bd081699ce39ce5887db7e612616014d . In that commit, package was forked to packages directory, then renamed, and added with `meteor add packagename`, where package name does not have character `:` +4. Use Browserstack.com to see errors at browser / inspect / console, or use iOS or other device emulators, to see error messages. Testing at real device is more important, because they could work differently than emulators, emulators sometimes do not emulate all same features. Those error messages have file where error happened, and line number, like `something.js:301` . From there, scroll up a little, look at what function or what package dependency it is where it happened. If possible, try to move that package serverside, like at step 1. Or alternatively, look is it possible to remove or change to some other compatible dependency. ## OLD: TODO