feat: fallback to non-compact when a package fails to use compact mode

[AmirSa12]

related to #402

[AmirSa12]

I'd like to know your thought about this, @aprendendofelipe. Thanks!

[continuous-releases-staging]

• example-1

• example-2

  npm i https://855c9e6b.stackblitz-cr.pages.dev/stackblitz-labs/pkg.pr.new/playground-a@450
  

  npm i https://855c9e6b.stackblitz-cr.pages.dev/stackblitz-labs/pkg.pr.new/playground-b@450
  

  npm i https://855c9e6b.stackblitz-cr.pages.dev/stackblitz-labs/pkg.pr.new/pkg-pr-new@450
  

commit: a62fb61

[aprendendofelipe]

Looks great! 🚀

Later on, we could consider a per-package fallback, possibly via an sb-compact-packages API header.

[AmirSa12]

Looks great! 🚀

Later on, we could consider a per-package fallback, possibly via an sb-compact-packages API header.

@aprendendofelipe As discussed internally, the npm is just for a feature ( --compact ) to check if we can make the url smaller, it's not for verification.
What do you think about making --compact obsolete by making that the default behavior, and if it fails, we just continue going with the long form? let me know your thoughts! Thanks

[aprendendofelipe]

This only affects the PR comment, correct?

I think it makes sense to make the compact URL the default, as long as there is still a way to opt into the long form.