Update test imports to use built files from dist directory

[yusifaliyevpro]

• Changed import paths in all test files to reference the built files in the dist directory instead of the source files in src.
• This change ensures that tests are run against the compiled code, improving reliability and consistency in testing.

Summary by CodeRabbit

• Chores

  • Updated and cleaned up package metadata, scripts, and dependencies.
  • Introduced workspace configuration for dependency management.
  • Adjusted workflow to remove the build step from pull request tests.

• Tests

  • Updated test imports to use the distribution build directory instead of the source directory.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This update restructures the project configuration by enhancing and cleaning up package.json, updating test imports to reference the distribution build, introducing a pnpm-workspace.yaml for workspace management, and modifying the PR test workflow to remove the build step. No changes were made to exported entities or source code logic.

Changes

Files / Group	Change Summary
.github/workflows/pr-test.yml	Removed the pnpm build step from the PR test workflow.
package.json	Restructured and enriched metadata, updated scripts, dependencies, and removed duplicates.
pnpm-workspace.yaml	Added new workspace config specifying onlyBuiltDependencies for unrs-resolver.
tests/*.test.ts	Changed imports from ../src to ../dist for all test files; no logic or assertion changes.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant GitHub Actions
    participant pnpm
    participant Jest

    Developer->>GitHub Actions: Open PR
    GitHub Actions->>pnpm: Install dependencies
    GitHub Actions->>pnpm: (Removed) Build step skipped
    GitHub Actions->>Jest: Run tests (using dist build)
    Jest-->>GitHub Actions: Report test results

Loading

Possibly related PRs

• Remove pull request test workflow and update .gitignore #21: Both PRs modify the pull request test workflow configuration in .github/workflows/pr-test.yml, with the main PR removing the build step and the retrieved PR removing the entire workflow file.
• Replace tsup with tsdown for build configuration #16: Both PRs update build tool configurations and package.json scripts, with a focus on switching to tsdown and managing workspace settings.
• Update dependencies for Node types and ts-jest #5: Both PRs update devDependencies in package.json, though the main PR does so more extensively.

Poem

A hop and a skip, the build step is gone,
Tests now run on dist, from dusk until dawn.
The package is tidy, the workspace is neat,
With pnpm in charge, our setup’s complete.
🐇✨
Hooray for the code that’s so easy to greet!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5222f67 and 93ca281.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (14)

• .github/workflows/pr-test.yml (0 hunks)
• package.json (2 hunks)
• pnpm-workspace.yaml (1 hunks)
• tests/getCountries.test.ts (1 hunks)
• tests/getCountriesByCodes.test.ts (1 hunks)
• tests/getCountriesByCurrency.test.ts (1 hunks)
• tests/getCountriesByLang.test.ts (1 hunks)
• tests/getCountriesByName.test.ts (1 hunks)
• tests/getCountriesByRegion.test.ts (1 hunks)
• tests/getCountriesBySubregion.test.ts (1 hunks)
• tests/getCountryByCapital.test.ts (1 hunks)
• tests/getCountryByCode.test.ts (1 hunks)
• tests/getCountryByDemonym.test.ts (1 hunks)
• tests/getCountryByTranslation.test.ts (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.