Jumping from Node v14 to v18 between 3.1.1 and 3.2.0 about rotating-file-stream HOT 6 CLOSED

@iccicci It works now - no warning when installing 3.2.1. Thank you!

from rotating-file-stream.

I forgot to update the README; thank you.

Anyway v3.2.0 simply adds intervalUTC option: if that's not needed, v3.2.0 is not needed as well.

BTW, older Node.js versions should be supported as well; forcing the installation of v3.2.0 reguardless from the engine version should make everything work as expected.

from rotating-file-stream.

Thanks for responding.

older Node.js versions should be supported as well

npm will report a warning that the package requests an unsupported engine version, so the only safe thing to do is to avoid installing that package version and limit it to something like 3.1.*.

from rotating-file-stream.

The only reason for the warning is this line: indeed is just a warning, not a blocking error.

In next days, I'll re-add support for Node.js v14; I hope this doesn't block your work even if for a few days.

from rotating-file-stream.

No worries - I restricted package version in my projects to 3.1.*, so I'm good for quite a while.

With regards to warning vs. error, perhaps there's a difference in interpretation, where those who treat this warning as such consider that the package in question will work with this version of Node, while it really means that the package requires this version because it introduces dependencies that the package requires, like new classes, encodings, etc. So, even though it's a warning, it is always a good practice to avoid installing packages that require higher version of Node than the current one.

Thanks for contemplating a fix for this. Much appreciated.

from rotating-file-stream.

Hi @gh-andre , v3.2.1 should solve this.

Please report here any other problems or close the issue if v3.2.1 actually solves.

Thank you

from rotating-file-stream.