-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Additional Mime Types #4
Comments
In related news, people need to start naming their things better: https://github.com/jsx/JSX Edit: Additionally, |
it's somewhere on their site that the mime type is |
@dougwilson @Fishrock123 you guys this this module is ready? should we start using htis |
@jonathanong yep! I said that when releasing 1.0.0 I think.. |
@jonathanong Yep, I've already started integrating it into various expressjs things. |
Awful, but it looks like facebook's Update: Yep, react hard-checks for that. https://github.com/facebook/react/blob/f230e0a03154e6f8a616e0da1fb3d97ffa1a6472/vendor/browser-transforms.js#L210 Landed in 168ea21 |
moving to mime-db |
Here's a list of additional mime types. You can make requests here, and we'll mark them as added and after some discussion and references.
.jsx
-http://facebook.github.io/react/docs/jsx-in-depth.html no idea, and i think there's an extension name conflicttext/jsx
- http://facebook.github.io/react/docs/getting-started.html.litcoffee
.ejs
.mustache
places to look for more:
The text was updated successfully, but these errors were encountered: