Excellent, thanks so much SuzieH! (And DougS!) Very helpful!
One thing I'm hoping to figure out (but will likely create a separate topic/thread for after doing some additional research) is performing some Sass linting before submitting the plugin (in an automated way using a CI build) to avoid any skin failures.
I've learned the hard way that submitting a skin via the SDK that has even a minor syntax error (e.g. typo in a variable name, etc.) will result in bricking the skin and showing an "unexpected error has occurred" message when loading the environment, which I want to avoid.
This is my current linting process in the SDK when ready to push up a change:
- I run li serve-sass and make sure it doesn't fail with any errors (as it tends to report errors that li submit-plugin doesn't catch that result in bricking the skin)
- I use Ctrl+C to stop the server that spins up in the previous step.
- I then run li submit-plugin to push the changes, again making sure nothing fails out with errors.
My hope is to find a linting process that will work within a CI build (i.e. automated / hands-off) so code isn't deployed and pushed to our Stage environment if it has issues.
Anyway, thanks again for your help in making this public!
