-
-
Notifications
You must be signed in to change notification settings - Fork 318
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
Apparently, the preferred mime-type for javascript is changing... #212
Comments
Interesting. Please file this with the https://github.com/jshttp/mime-db project. That's where this module pulls it's MIME definitions from. |
See jshttp/mime-db#194. |
Just for clarification, does this package need to do anything extra to receive the now updated .js MIME type from the "mime-db" registry? |
I do need to update the Ping me here when that happens and I'll push a new release. cc @dougwilson (for update on when to expect a new release) |
Ahhh, I just saw that the issue tracking it had been closed, but didn't realize that the release hadn't happened. Since that issue was also locked, I don't expect it will get any more notifications when such a release happens. Hopefully @dougwilson can let us know here when it does. :) |
Hi @broofa , I will let you know. I recently went to make a release, but found nvm is broken for our build. I opened an issue on nvm and the issue is fixed, but nvm has not yet made a release with the fix. I will get a new mime-db releaased as soon as that happens 👍 |
In this thread, and more specifically here, apparently the long-held preference of
application/javascript
is switching totext/javascript
.It would be appreciated if this utility would update accordingly.
The text was updated successfully, but these errors were encountered: