(test): fixing tests node v18

[vagostep]

This PR solves #117

Tagging 3 tests as deprecated because, there are not longer valid.

the method path.normalize() will normalize them and, therefore, the expected scenarios are not going to happen anymore.

I could delete them, but first I would like your opinion.

Tested up to Node v22

[UlisesGascon]

Thanks @vagostep! I like to see how fast you started to do contributions ✨

I was thinking that we can keep the tests and just pass them when the Node.js version is major or equal to 18.16.0, so that way we don't lost these test for retrocompatibility. WDYT?

I changed the runner in 8cf1c4f so we can test this PR here directly 👍

Note: there are some linting issues too

[vagostep]

@UlisesGascon

I was thinking that we can keep the tests and just pass them when the Node.js version is major or equal to 18.16.0, so that way we don't lost these test for retrocompatibility. WDYT?

I ran the test downgrading the Node version down to V16 and still the tests are failing. I'm going to try to identify since which version they started to fail

Note: there are some linting issues too

Checking it!

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​eslint/​eslintrc@​0.4.3 ⏵ 3.3.1	+1		+12
	@​eslint/​js@​9.27.0
	eslint@​7.23.0 ⏵ 9.27.0				+1

View full report

[vagostep]

Hi guys. I just pushed new changes:

• updating eslint package and, therefore, the lint errors were solved
• adding a condition to run the broken test if the node version is lower than a base.

I could not find from which node version the test started to fail :/ without manually downgrade each package in the package.json to make them work. I only could test them until Node v16 and the test were still broken

I'm open to suggestion about how can I proceed

[vagostep]

@bjohansebas linter continued marking me this line as error. I could not find a workaround

[bjohansebas]

I recommend not updating the linter yet, there's a broader discussion around it (see expressjs/discussions#327)

[vagostep]

Got it. I'll revert it

[vagostep]

closing in order to use #120