- From: snuggs <notifications@github.com>
- Date: Mon, 24 Jul 2017 02:11:16 +0000 (UTC)
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 24 July 2017 02:11:39 UTC
> ES6 module imports require MIME type to be specifically JavaScript (e.g. application/javascript etc.) - @TakayoshiKochi Is this inclusive of `application/ecmascript`? Although considered the [official ECMAScript MIME type in rfc4392](https://tools.ietf.org/html/rfc4329#section-8.2) often servers respond with OCTET streams and/or often goes unrecognized by browser. I know this is a corner case but curious of any caveats people like myself who utilize `application/ecmascript` MIME types along with `.es` extension within certain HTTP responses based on [Content Negotiation](https://en.wikipedia.org/wiki/Content_negotiation). If modules would require explicit `application/ecmascript` would like to know sooner than later so can adjust accordingly. Thanks in advance! 🙏 -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/645#issuecomment-317302405
Received on Monday, 24 July 2017 02:11:39 UTC