Simple component-exists check to avoid throwing exceptions #3
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
My Svelte-in-Blaze app was sometimes throwing errors in this part of
SvelteComponent.js:My guess is that the template was getting destroyed before it had a chance to be rendered. I don't know why, but adding a check to see if
this.componentexists before calling.$destroy()seemed like an easy and pragmatic solution. Seems to be working well now with no side effects that I can detect.