Fix #1409 and Fix #1410: "use server" case, and $ starting variable.

[samchon]

Emergent update for #1409 and #1410.

---

This pull request includes several updates across multiple files to improve consistency and functionality. The most important changes involve renaming identifiers for clarity, updating functions, and adding new validation and testing capabilities.

Version Update:

• package.json: Updated the version from 7.0.0 to 7.0.1.

Function and Identifier Renaming:

• src/internal/_miscCloneAny.ts: Renamed the $cloneMain function to cloneMain throughout the file for consistency. [1] [2]
• src/programmers/ValidateProgrammer.ts: Renamed the $report identifier to _report for better readability and consistency. [1] [2] [3]
• test/generate/output/generate_http.ts: Renamed $report to _report in multiple locations for consistency. [1] [2] [3]
• test/generate/output/generate_json.ts: Renamed $report to _report in multiple locations for consistency. [1] [2] [3] [4] [5] [6]

New Functions and Enhancements:

• src/transformers/FileTransformer.ts: Added the find_import_injection_index function to determine the correct index for import injection, improving the file transformation process. [1] [2]

Testing and Validation:

• test/build/validate-generate.ts: Added a new test to ensure that files do not contain the ` character, which is not allowed in Svelte5.
• test/generate/input/generate_index.ts: Added a new test file with multiple validation functions for the ICitizen interface.
• test/generate/input/generate_use.ts: Added a new test file with strict mode and server usage declarations.

[pkg-pr-new]

Open in Stackblitz

npm i https://pkg.pr.new/typia@1411

commit: 2f7c9af

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher

🚮 Removed packages: npm/lz-string@1.5.0, npm/monaco-editor@0.50.0, npm/next-sitemap@4.2.3, npm/next@14.2.18, npm/nextra-theme-docs@2.13.4, npm/nextra@2.13.4, npm/path@0.12.7, npm/process@0.11.10, npm/react-dom@18.3.1, npm/react@18.3.1, npm/tgrid@1.1.0, npm/ts-loader@9.5.1, npm/typedoc-github-theme@0.1.2, npm/typedoc@0.26.11, npm/typescript@5.7.2, npm/typia@7.0.0, npm/write-file-webpack-plugin@4.5.1

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	CI
Possible typosquat attack	npm/emoji-regex-xs@1.0.0	Did you mean: emoji-regex~~-xs~~	⚠︎

View full report↗︎

Next steps

What is a typosquat?

Package name is similar to other popular packages and may not be the package you want.

Use care when consuming similarly named packages and ensure that you did not intend to consume a different package. Malicious packages often publish using similar names as existing popular packages.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/emoji-regex-xs@1.0.0

[samchon]

OK.