Some may know I have a rather unusual setup that requires symlinking the storage folder to the uploads folder to work with Pantheon. Although I have gotten this to work, there are inconsistencies between Lando running Sage 10 via yarn start locally, and what I see on Pantheon’s dev server. In theory, there shouldn’t be, unless the storage folder itself needs to be synced. Can someone let me know if that is true? I don’t know enough about the storage folder to really know if that is the issue.
The other inconsistencies I am seeing is that, for instance, @Log1x’s log1x/sage-directives package works fine in regards to using directives in blade templates for ACF fields, but using the directives from his other log1x/sage-svg package works locally, but not on Pantheon’s dev server. The work around is using the helper function, which works both locally and remotely on Pantheon’s dev server.
Another odd inconsistency is that, if I pull the latest db/code/files from Pantheon’s dev server, via lando pull and run a yarn start it seems to have cached old template code. I have to hunt around to find which file is cached in VSCode to merely hit ‘save’ with no changes, get webpack to rebuild and the browser reloads properly. Finally, my footer does not work locally, but shows up on dev perfectly fine. 
If someone can review my install process, and maybe point out if there was a flaw from the beginning causing this, or that if I blow out caching somewhere and restart X that might do the trick, I would really appreciate it. Really, any thoughts on this would be great. I absolutely am in love with this workflow aside these inconsistencies. I will also admit I am new to composer. I come from the node world and liken it to package.json and node_modules. There is something I am missing due to my lack of knowledge here, or at least that’s my guess. I am hoping other eyes will see something I am missing, or did not think of.
Thanks for looking!
Frank
