refactor: remove node's path to be able to use in client

[daniil4udo]

No description provided.

[IamLizu]

Interesting but there are edge cases for example with trailing slashes, it will return empty string. path does some sort of input validation and error handling like if you pass null or undefined in path.basename() it is handled.

Moreover, content disposition is fundamentally a server-side mechanism in the HTTP protocol (response headers) that instructs client (browser) on how to handle the content. It should be controlled by the server.

[daniil4udo]

Good call. I've refined it.

You're correct that Content-Disposition is defined as a server-side mechanism in the HTTP protocol, intended to instruct the client on handling the content. However, the protocol's client-side behavior opens up valid use cases for parsing this header on the client side. For example, extracting filenames from Content-Disposition is a common scenario when saving files downloaded via JavaScript in web applications.

Consider modern use cases where APIs serve files, and the client handles saving them. In such scenarios, the server provides Content-Disposition as metadata, but the client's role in interpreting it is equally critical for enabling seamless user experiences. While the server controls the header's value, parsing it client-side doesn't violate the protocol—it's merely leveraging the metadata for practical application.

In essence, both server and client share responsibilities in the broader mechanism, making client-side parsing a practical and legitimate extension of the standard's utility