Closed aldy505 closed 4 months ago
should we also downgrade @types/node
to v16?
should we also downgrade
@types/node
to v16?
@trim21 No need, right? We're bundling everything with Babel anyway.
should we also downgrade
@types/node
to v16?@trim21 No need, right? We're bundling everything with Babel anyway.
we didn't bundle anything
should we also downgrade
@types/node
to v16?@trim21 No need, right? We're bundling everything with Babel anyway.
we didn't bundle anything
I thought Babel was for transpiling to older Nodejs versions, no?
should we also downgrade
@types/node
to v16?@trim21 No need, right? We're bundling everything with Babel anyway.
we didn't bundle anything
I thought Babel was for transpiling to older Nodejs versions, no?
yes, transpiling only
should we also downgrade
@types/node
to v16?@trim21 No need, right? We're bundling everything with Babel anyway.
we didn't bundle anything
I thought Babel was for transpiling to older Nodejs versions, no?
yes, transpiling only
Ah that should be good enough.
Can I have this reviewed, please? @kaankabalak @prakashsvmx
the CI still looks for tests on old version of node 12 on windows/ubuntu
Test on node 12.x and ubuntu-latest
Test on node 12.x and windows-latest
We will check this. @aldy505
@prakashsvmx Hi, any updates?
I think it requires some admin access at the org level , i will check further.
should also remove file https://github.com/minio/minio-js/blob/master/src/internal/async.ts ....
On the
package.json
file, it is defined that the minimum of Node.js version is 16. So it makes sense to drop version 12 and 14.https://github.com/minio/minio-js/blob/51cf376d29d805e8b2aae02653cf1779817409ad/package.json#L75-L77