fix(js_semantic):handle exported modules and their members

[Conaclos]

Summary

Fixes #4179.

This also recognize exported members of a module.

Test Plan

Test included.
By the way I am not sure to understand why noUnusedVariables is not in tests/specs.

• The PR requires documentation
• I will create a new PR to update the documentation

[netlify]

✅ Deploy Preview for docs-rometools canceled.

Built without sensitive environment variables

Name	Link
🔨 Latest commit	eb22d23
🔍 Latest deploy log	https://app.netlify.com/sites/docs-rometools/deploys/63eac5631f0b1500089a6064

[ematipico]

@Conaclos the tests are under the folder: https://github.com/rome/tools/tree/main/crates/rome_js_analyze/tests/specs/correctness/noUnusedVariables

You can create a file with the same name as a rule or a folder. Having a folder allows the creation of more test cases

[ematipico]

What's the reason behind the deleted code?

[Conaclos]

@Conaclos the tests are under the folder: https://github.com/rome/tools/tree/main/crates/rome_js_analyze/tests/specs/correctness/noUnusedVariables

You can create a file with the same name as a rule or a folder. Having a folder allows the creation of more test cases

Actually, the tests are located in rome_js_analyze/tests/suppression/correctness/noUnusedVariables. The folder was preexisting. My question was why rome_js_analyze/tests/suppression instead of rome_js_analyze/tests/specs?

[ematipico]

My question was why rome_js_analyze/tests/suppression instead of rome_js_analyze/tests/specs?

Clearly an issue :D it should not be there

[Conaclos]

What's the reason behind the deleted code?

This handles exports in modules and namespaces. The removed check restricted the analysis to exports at the ESM level.

As a example:

expot const Z ="Z" // esm level export
export namespace M1 { // esm level export
  export const X = "X" // inner eexport
  export namespace M2 { // inner eexport
    export const Y = "Y" // inner eexport
  }
}