-
Notifications
You must be signed in to change notification settings - Fork 11
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
mime package is getting esm only #60
Comments
It still fine by using dynamic import. |
We can stay on the old version for as long as we want. |
Mime 3.0 is broken right now, package managers are complaining about it, should update to 4.0 |
What are they complaining about? All is fine on my end |
I guess it sounds a good idea for a fork and embed the types 🫠😅 |
I can do this, but after Wednesday So someone else who is willing can do it before |
I don't understand the problem here. @thelinuxlich |
You don't but TS checks for it when interacting with the mime sub dependency |
This comment was marked as outdated.
This comment was marked as outdated.
Here is the minimal check to see if missing Can you provide the usage showing the error you mention? index.ts import { send } from '@fastify/send'
import { createServer } from 'node:http'
createServer(function onRequest(req, res) {
send(req, './index.ts')
.pipe(res)
}).listen(3000) package.json {
"name": "repo",
"version": "1.0.0",
"description": "",
"main": "index.js",
"scripts": {
"dev": "ts-node index.ts",
"build": "tsc index.ts"
},
"author": "",
"license": "ISC",
"dependencies": {
"@fastify/send": "^2.1.0"
},
"devDependencies": {
"@types/node": "^20.12.2",
"ts-node": "^10.9.2",
"typescript": "^5.4.3"
}
} tsconfig.json {
"compilerOptions": {
"strict": true
}
} |
Here's another package using the same version and impacted by mime 3.0 on TS : googleapis/nodejs-storage#2434 |
Another one: firebase/firebase-admin-node#2512 |
I don't see For None of your issue show the issue exist inside this repository. |
Prerequisites
Issue
We depend on mime. Some people would like to see the world break. Maybe we should avoid that...
The text was updated successfully, but these errors were encountered: