fix(legacy)!: should rename x.[hash].js to x-legacy.[hash].js

[aleen42]

Description

The previous regex has renamed x.[hash].js to x.[hash]-legacy.js.

Additional context

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines and follow the PR Title Convention.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

[patak-dev]

Would you create a test that reproduces this issue?

[aleen42]

@patak-dev I have changed the implementation, which will be smarter when meeting [hash].

[jiadesen]

@aleen42 @patak-dev
Although this is a trivial problem, the new rule here will produce the following weird file names:

[hash].js -> -legacy[hash].js

eg:

->

v4:

[patak-dev]

I think it would be good to fix this, @jiadesen would you open a proper issue (and later a PR if you'd like) for this? Maybe we should revert to v4 if there is no [name] in the pattern

[jiadesen]

ok, I can try it