mincho-js / mincho

Natural CSS in TypeScript
MIT License
40 stars 0 forks source link

Configure bundler settings #36

Closed black7375 closed 3 months ago

black7375 commented 3 months ago

Description

Implement #35 Resolve various dependency and bundling issues.

I also pluginised to make it easier to use debugLog during testing.

Summary by CodeRabbit

github-actions[bot] commented 3 months ago

Triggered from https://github.com/mincho-js/mincho/pull/36 by @​black7375.

Checking if we can fast forward main (cc6e3c6cfcee19f7d654b0389ac1e0076fbcfd22) to bundler-setup (50fdebad5bbb13bb2a2ebe48edbac848d4454164).

Target branch (main):

commit cc6e3c6cfcee19f7d654b0389ac1e0076fbcfd22 (HEAD -> main, origin/main, origin/HEAD)
Author: alstjr7375 <alstjr7375@daum.net>
Date:   Wed Jul 17 15:52:17 2024 +0900

    Chore: Console debug package #33

Pull request (bundler-setup):

commit 50fdebad5bbb13bb2a2ebe48edbac848d4454164 (pull_request/bundler-setup)
Author: alstjr7375 <alstjr7375@daum.net>
Date:   Fri Jul 19 17:07:06 2024 +0900

    Clean: Config formatting #35

It is possible to fast forward main (cc6e3c6cfcee19f7d654b0389ac1e0076fbcfd22) to bundler-setup (50fdebad5bbb13bb2a2ebe48edbac848d4454164). If you have write access to the target repository, you can add a comment with /fast-forward to fast forward main to bundler-setup.

coderabbitai[bot] commented 3 months ago

Walkthrough

This update introduces several new configuration files for Visual Studio Code, enhancing the development environment for JavaScript and TypeScript projects. Key additions include recommended extensions for linting and formatting, tailored editor settings, and refined ESLint and TypeScript configurations. These changes simplify setup, improve code quality, and ensure a consistent coding experience across the team.

Changes

Files Change Summary
configs/eslint-config-custom/.vscode/extensions.json
configs/vite-config-custom/.vscode/extensions.json
New configuration files that recommend ESLint and Prettier extensions for improved linting and formatting in Visual Studio Code.
configs/eslint-config-custom/.vscode/settings.json
configs/vite-config-custom/.vscode/settings.json
New settings files enhancing editor behavior, auto-saving, TypeScript SDK configurations, and ESLint integration for a better developer experience.
configs/eslint-config-custom/eslint.config.base.js Reformatted the ignores array for improved readability without changing functionality.
configs/tsconfig-custom/tsconfig.json Added @mincho/debug-log/importMeta to the types array for enhanced type definitions and IntelliSense support.
configs/vite-config-custom/index.d.ts Narrowed TInputConfig type to the first parameter of the defineConfig function for better type safety.
configs/vite-config-custom/index.js Enhanced build configuration with TypeScript checks, added output paths for declaration files, and refined plugin handling to better support both ES and CommonJS formats.
configs/vite-config-custom/package.json Updated devDependencies to include a custom Prettier configuration and a new plugin for externalizing dependencies.
packages/debug-log/importMeta.d.ts Introduced a new interface ImportMeta extending TypeScript capabilities for debugging functionalities.
packages/debug-log/package.json Updated module paths and added importMeta.d.ts for better structure and clarity in exports.
packages/transform-to-vanilla/package.json Adjusted paths for typings and exports for consistency across module formats.
turbo.json Modified lint and test sections to enhance task dependencies, ensuring linting occurs after building.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant VSCode
    participant ESLint
    participant Prettier
    participant BuildSystem

    Developer->>VSCode: Open project
    VSCode->>ESLint: Check code quality
    VSCode->>Prettier: Format code
    Developer->>BuildSystem: Run build
    BuildSystem->>ESLint: Run linting
    BuildSystem->>Prettier: Run formatting
    Developer->>BuildSystem: Test changes

🐰 In a world where codes entwine,
A rabbit hops with joy divine.
With settings and paths all in line,
Our code will flourish, oh so fine!
Extensions sprout like flowers in spring,
Together we'll code, let the laughter ring! 🌸


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share - [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)
Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `Generate unit testing code for this file.` - `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 generate unit testing code for this file.` - `@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 generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@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.` 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 as 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 resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.
black7375 commented 3 months ago

/fast-forward

github-actions[bot] commented 3 months ago

Triggered from https://github.com/mincho-js/mincho/pull/36#issuecomment-2238685948 by @​black7375.

Trying to fast forward main (cc6e3c6cfcee19f7d654b0389ac1e0076fbcfd22) to bundler-setup (50fdebad5bbb13bb2a2ebe48edbac848d4454164).

Target branch (main):

commit cc6e3c6cfcee19f7d654b0389ac1e0076fbcfd22 (HEAD -> main, origin/main, origin/HEAD)
Author: alstjr7375 <alstjr7375@daum.net>
Date:   Wed Jul 17 15:52:17 2024 +0900

    Chore: Console debug package #33

Pull request (bundler-setup):

commit 50fdebad5bbb13bb2a2ebe48edbac848d4454164 (pull_request/bundler-setup)
Author: alstjr7375 <alstjr7375@daum.net>
Date:   Fri Jul 19 17:07:06 2024 +0900

    Clean: Config formatting #35

Fast forwarding main (cc6e3c6cfcee19f7d654b0389ac1e0076fbcfd22) to bundler-setup (50fdebad5bbb13bb2a2ebe48edbac848d4454164).

$ git push origin 50fdebad5bbb13bb2a2ebe48edbac848d4454164:main
To https://github.com/mincho-js/mincho.git
   cc6e3c6..50fdeba  50fdebad5bbb13bb2a2ebe48edbac848d4454164 -> main