title: Do esm.sh and jspm.org follow the same approach regarding deno compatibility?
body: <p>I've seen deno examples importing npm modules both from esm.sh and jspm.org</p>
  <p>In esm.sh I read:</p>
  <blockquote>
  <ul>
  <li>esm.sh will polyfill the node internal modules(fs,os,etc) with <a href="https://deno.land/std/node" rel="nofollow noreferrer">https://deno.land/std/node</a> to support some modules to work in Deno, like <code>postcss</code></li>
  <li>By default, esm.sh will response a custom HTTP header of X-TypeScript-Types when the types(dts) defined, that is useful for deno types check</li>
  </ul>
  </blockquote>
  <p>Does jspm.org follow the same approach?</p>
  <p>Which one is less likely to cause issues when importing npm modules in deno?</p>