Debug environment #34
Conversation
|
Triggered from #34 by @black7375. Checking if we can fast forward Target branch ( commit 9b79c35d58008bbd0dc7c06139db54edc3e1cc49 (HEAD -> main, origin/main, origin/HEAD)
Author: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Date: Mon Jul 15 09:31:11 2024 +0000
Chore(deps): Bump the npm_and_yarn group with 2 updates
Bumps the npm_and_yarn group with 2 updates: [braces](https://github.com/micromatch/braces) and [tar](https://github.com/isaacs/node-tar).
Updates `braces` from 3.0.2 to 3.0.3
- [Changelog](https://github.com/micromatch/braces/blob/master/CHANGELOG.md)
- [Commits](https://github.com/micromatch/braces/compare/3.0.2...3.0.3)
Updates `tar` from 6.2.0 to 6.2.1
- [Release notes](https://github.com/isaacs/node-tar/releases)
- [Changelog](https://github.com/isaacs/node-tar/blob/main/CHANGELOG.md)
- [Commits](https://github.com/isaacs/node-tar/compare/v6.2.0...v6.2.1)
---
updated-dependencies:
- dependency-name: braces
dependency-type: indirect
dependency-group: npm_and_yarn
- dependency-name: tar
dependency-type: indirect
dependency-group: npm_and_yarn
...
Signed-off-by: dependabot[bot] <support@github.com>Pull request ( commit b42a54d0159ccff2543de0eb9740b4b07bac852d (pull_request/debugging)
Author: alstjr7375 <alstjr7375@daum.net>
Date: Wed Jul 17 15:52:17 2024 +0900
Chore: Console debug package #33Can't fast forward * b42a54d0159ccff2543de0eb9740b4b07bac852d Chore: Console debug package #33
* 796ed7f0fc78b251346fe3f2a1113c933d56e7c3 Chore: Launching debugging mode improves performance and applies to all packages #33
* 19c2168d56e071ae2186a150bb8fb4f6b38b435d Chore: Debugger setup for VS Code #33
| * 9b79c35d58008bbd0dc7c06139db54edc3e1cc49 Chore(deps): Bump the npm_and_yarn group with 2 updates
|/
* 1f8794aa20d9a3f5e1dee1465ccb6372483dc59e Chore: Action - Activate fast-forward merge
commit 1f8794aa20d9a3f5e1dee1465ccb6372483dc59e
Author: alstjr7375 <alstjr7375@daum.net>
Date: Mon Jul 15 18:14:15 2024 +0900
Chore: Action - Activate fast-forward merge
See https://github.com/marketplace/actions/fast-forward-mergeRebase locally, and then force push to |
WalkthroughThis update primarily introduces several new utilities and configurations across multiple packages. Key changes include the addition of Changes
Poem
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? TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Additionally, you can add CodeRabbit Configuration File (
|
|
Triggered from #34 by @black7375. Checking if we can fast forward Target branch ( commit 9b79c35d58008bbd0dc7c06139db54edc3e1cc49 (HEAD -> main, origin/main, origin/HEAD)
Author: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Date: Mon Jul 15 09:31:11 2024 +0000
Chore(deps): Bump the npm_and_yarn group with 2 updates
Bumps the npm_and_yarn group with 2 updates: [braces](https://github.com/micromatch/braces) and [tar](https://github.com/isaacs/node-tar).
Updates `braces` from 3.0.2 to 3.0.3
- [Changelog](https://github.com/micromatch/braces/blob/master/CHANGELOG.md)
- [Commits](https://github.com/micromatch/braces/compare/3.0.2...3.0.3)
Updates `tar` from 6.2.0 to 6.2.1
- [Release notes](https://github.com/isaacs/node-tar/releases)
- [Changelog](https://github.com/isaacs/node-tar/blob/main/CHANGELOG.md)
- [Commits](https://github.com/isaacs/node-tar/compare/v6.2.0...v6.2.1)
---
updated-dependencies:
- dependency-name: braces
dependency-type: indirect
dependency-group: npm_and_yarn
- dependency-name: tar
dependency-type: indirect
dependency-group: npm_and_yarn
...
Signed-off-by: dependabot[bot] <support@github.com>Pull request ( commit cc6e3c6cfcee19f7d654b0389ac1e0076fbcfd22 (pull_request/debugging)
Author: alstjr7375 <alstjr7375@daum.net>
Date: Wed Jul 17 15:52:17 2024 +0900
Chore: Console debug package #33It is possible to fast forward |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
Outside diff range, codebase verification and nitpick comments (3)
packages/transform-to-vanilla/.vscode/settings.json (1)
3-4: Approved TypeScript settings in VS Code configuration.The settings to enable the use of the workspace TypeScript SDK and the specific path setting ensure that the development environment is consistent across different setups.
Consider centralizing common VS Code settings across packages to reduce redundancy and simplify maintenance.
packages/debug-log/src/index.ts (2)
10-26: Review customconsolaimplementation.The custom
consolaobject is implemented to handle logging. Ensure that this implementation is robust and consider whether it could benefit from further abstraction or if it might be better to use the originalconsolaonce the issue is resolved.
31-33: Review thegetCountfunction.The
getCountfunction is used to generate a unique debug identifier. Ensure that this implementation is thread-safe and consider using a more robust method for generating unique identifiers if necessary.
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (2)
.yarn/patches/pretify-deep-diff-npm-1.0.1-587f0078e3.patchis excluded by!**/.yarn/**yarn.lockis excluded by!**/yarn.lock,!**/*.lock
Files selected for processing (24)
- package.json (1 hunks)
- packages/css-additional-types/.vscode/extensions.json (1 hunks)
- packages/css-additional-types/.vscode/launch.json (1 hunks)
- packages/css-additional-types/.vscode/settings.json (1 hunks)
- packages/css-additional-types/package.json (1 hunks)
- packages/css/.vscode/extensions.json (1 hunks)
- packages/css/.vscode/launch.json (1 hunks)
- packages/css/.vscode/settings.json (1 hunks)
- packages/css/package.json (1 hunks)
- packages/debug-log/.editorconfig (1 hunks)
- packages/debug-log/.vscode/extensions.json (1 hunks)
- packages/debug-log/.vscode/launch.json (1 hunks)
- packages/debug-log/.vscode/settings.json (1 hunks)
- packages/debug-log/README.md (1 hunks)
- packages/debug-log/eslint.config.js (1 hunks)
- packages/debug-log/package.json (1 hunks)
- packages/debug-log/src/index.ts (1 hunks)
- packages/debug-log/tsconfig.json (1 hunks)
- packages/debug-log/tsconfig.node.json (1 hunks)
- packages/debug-log/vite.config.ts (1 hunks)
- packages/transform-to-vanilla/.vscode/extensions.json (1 hunks)
- packages/transform-to-vanilla/.vscode/launch.json (1 hunks)
- packages/transform-to-vanilla/.vscode/settings.json (1 hunks)
- packages/transform-to-vanilla/package.json (1 hunks)
Files skipped from review due to trivial changes (6)
- packages/css/.vscode/settings.json
- packages/debug-log/.editorconfig
- packages/debug-log/.vscode/extensions.json
- packages/debug-log/.vscode/settings.json
- packages/debug-log/tsconfig.json
- packages/debug-log/tsconfig.node.json
Additional comments not posted (20)
packages/debug-log/eslint.config.js (1)
1-3: Verify import path for TypeScript ESLint configurationThis file exports a TypeScript ESLint configuration from
eslint-config-custom/typescript. Ensure that the moduleeslint-config-custom/typescriptis correctly installed and accessible in the project's dependencies.Verification successful
Verify import path for TypeScript ESLint configuration
The module
eslint-config-customis listed in the devDependencies, and it exports the requiredtypescriptconfiguration. Therefore, the import patheslint-config-custom/typescriptshould be valid.
eslint-config-customis listed in thedevDependenciesof multiplepackage.jsonfiles.- The
eslint-config-custompackage exports thetypescriptconfiguration.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Check if the module 'eslint-config-custom/typescript' is installed. # Test: Search for the module in package.json files. Expect: At least one match. rg --type json '"eslint-config-custom/typescript"' --files-with-matches package.jsonLength of output: 86
Script:
#!/bin/bash # Description: Check for 'eslint-config-custom/typescript' in dependencies or devDependencies in all package.json files. # Search for the module in dependencies or devDependencies sections of package.json files. rg --type json '"eslint-config-custom/typescript"' -A 5 package.jsonLength of output: 70
Script:
#!/bin/bash # Description: List all package.json files and inspect their contents for any reference to 'eslint-config-custom/typescript'. # Find all package.json files. fd package.json --exec catLength of output: 9646
packages/debug-log/vite.config.ts (1)
1-8: Verify the usage ofNodeConfigin Vite configurationThis file uses
NodeConfigfromvite-config-customto configure Vite for a Node environment. Verify thatNodeConfigis properly defined invite-config-customand that it operates correctly with theConfigEnvtype from Vite.packages/css-additional-types/.vscode/extensions.json (1)
8-10: Approve addition of new VS Code extensionsThe additions of "augustocdias.tasks-shell-input" and "vitest.explorer" to the recommended extensions list are approved.
It might be beneficial to verify the utility of these extensions in the context of the project to ensure they align with the development needs.
packages/css/.vscode/extensions.json (1)
8-10: Approve addition of new VS Code extensionsThe additions of "augustocdias.tasks-shell-input" and "vitest.explorer" to the recommended extensions list are approved.
It might be beneficial to verify the utility of these extensions in the context of the project to ensure they align with the development needs.
packages/transform-to-vanilla/.vscode/extensions.json (1)
9-10: Approved addition of new VS Code extensions.The extensions "augustocdias.tasks-shell-input" and "vitest.explorer" are added to enhance task input handling and testing visualization, respectively.
Please ensure to verify the impact of these extensions on the developer workflow, particularly in terms of performance and utility.
packages/css-additional-types/.vscode/settings.json (1)
3-4: Approved TypeScript settings in VS Code configuration.The settings to enable the use of the workspace TypeScript SDK and the specific path setting ensure that the development environment is consistent across different setups.
packages/css/package.json (1)
29-29: Approved addition of@mincho/debug-logto development dependencies.This addition aligns with the PR's objectives to enhance debugging capabilities.
Please verify the maintenance status and compatibility of
@mincho/debug-logwith the project.packages/css-additional-types/package.json (1)
28-28: Approved addition of@mincho/debug-logdependency.The addition of
@mincho/debug-logtodevDependenciesis appropriate for enhancing debugging capabilities as outlined in the PR objectives. Ensure that the version specified ("workspace:^") aligns with your workspace management strategy.packages/debug-log/README.md (1)
1-41: Comprehensive and clear README fordebug-log.The README provides a clear description of the package's functionality and usage. The inclusion of images and code samples enhances understanding. Ensure the images are hosted in a reliable location to prevent future broken links.
packages/transform-to-vanilla/package.json (1)
48-48: Approved addition of@mincho/debug-logdependency.The addition of
@mincho/debug-logtodevDependenciesis consistent with the project's aim to enhance debugging capabilities. Verify that the version specified ("workspace:^") is correctly managed within your workspace.packages/debug-log/package.json (1)
1-51: Well-configured package.json fordebug-log.The package.json file is well-structured with appropriate scripts and dependencies for the
debug-logpackage. Ensure that all dependencies are necessary and that there are no redundant or conflicting packages.packages/css-additional-types/.vscode/launch.json (1)
1-62: Comprehensive Review of New Debug Configuration
Documentation and Links: The comments and links provided for guidance on debugging and performance improvements are helpful for developers unfamiliar with the settings.
Configuration Settings:
- General Settings: The
type,request, andnamefields are correctly set for Node.js debugging.- Path Settings: The use of
${input:GIT_ROOT}to dynamically set theprogrampath is a good practice, ensuring flexibility and correctness in different environments.- Debugging Flags: The arguments like
--no-isolateand--no-file-parallelismare appropriate for a testing environment where isolation of modules might not be necessary and could hinder debugging.Potential Improvements:
- Redundant Settings: Both configurations are very similar except for the remote debugging flags. Consider combining them or abstracting common settings to reduce redundancy.
- Extension Dependency: The dependency on
augustocdias.tasks-shell-inputfor executing shell commands should be documented in the project's README or setup guide to ensure all developers can utilize these configurations without issues.Overall, the configurations are well-structured and serve the intended purpose of enhancing the debugging experience. However, ensuring that all developers are aware of the dependencies and setup requirements is crucial for effective use.
packages/css/.vscode/launch.json (1)
1-62: Identical Debug Configuration as Previous PackageThis configuration file is identical to the one reviewed in the
packages/css-additional-typesdirectory. If this redundancy is intentional and each package requires a separate debugging configuration, the settings are correct and follow best practices as previously noted.However, if the packages can share a common configuration, consider centralizing these settings to reduce maintenance overhead and potential inconsistencies in the future.
packages/debug-log/.vscode/launch.json (1)
1-62: Repeated Debug Configuration Across PackagesAs with the previous packages, this configuration file is identical. If separate configurations are necessary for each package, they are set up correctly. However, consider the possibility of centralizing these settings to a common configuration file if applicable, to streamline the setup and maintenance.
packages/transform-to-vanilla/.vscode/launch.json (1)
1-62: Consistent Yet Redundant Debug ConfigurationThis file, like the others reviewed, contains identical debugging configurations. While consistency is beneficial, especially in larger projects, consider whether these configurations could be centralized or if there is a specific reason each package must have its own distinct configuration file.
package.json (1)
62-62: Verify the correctness of the new resolution forpretify-deep-diff.The resolution for
pretify-deep-diff@npm:^1.0.0has been added to patch a specific version. Ensure that this patch is necessary and correctly references the intended version.Verification successful
Let's verify the correctness of the new resolution for
pretify-deep-diffby inspecting thepackage.jsonfor the correct version reference.
Verified the correctness of the new resolution for
pretify-deep-diff.The patch file exists, and the
package.jsoncorrectly references the intended version1.0.1with the patch applied.
- The patch file
.yarn/patches/pretify-deep-diff-npm-1.0.1-587f0078e3.patchis present and contains relevant changes.- The
package.jsoncorrectly resolvespretify-deep-diff@npm:^1.0.0topatch:pretify-deep-diff@npm%3A1.0.1#~/.yarn/patches/pretify-deep-diff-npm-1.0.1-587f0078e3.patch.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify if the patch file exists and inspect its contents. # Test: Check if the patch file exists. Expect: File exists. cat .yarn/patches/pretify-deep-diff-npm-1.0.1-587f0078e3.patchLength of output: 1600
Script:
#!/bin/bash # Description: Verify if the package.json correctly references the intended version for pretify-deep-diff. # Test: Check the version resolution for pretify-deep-diff in package.json. Expect: Correct version reference. cat package.json | jq '.resolutions["pretify-deep-diff@npm:^1.0.0"]'Length of output: 169
packages/debug-log/src/index.ts (4)
52-60: Review thejsonLogfunction.The
jsonLogfunction combinesdebugLogandjsonPrintto log JSON data. Ensure that the integration of these functions is seamless and that the function handles various data types correctly.Verification successful
The
jsonLogfunction integratesdebugLogandjsonPrintcorrectly. The implementations ofdebugLogandjsonPrinthandle various data types and log them appropriately, ensuring seamless integration withinjsonLog.
debugLogformats and logs a message usingconsola.infoandchalk.bold.jsonPrintconverts the input to a JSON string, appliescolorize, and logs it usingconsola.box.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the integration of `debugLog` and `jsonPrint` in `jsonLog`. # Test: Log different types of JSON data. Expect: Correct logging. echo '{"key": "value"}' | node -e 'require("./index").jsonLog(process.stdin)'Length of output: 151
Script:
#!/bin/bash # Search for the definition of `debugLog` ast-grep --lang typescript --pattern 'function debugLog($_$$$) { $$$ }' # Search for the definition of `jsonPrint` ast-grep --lang typescript --pattern 'function jsonPrint($_$$$) { $$$ }'Length of output: 148
Script:
#!/bin/bash # Search for the definition of `debugLog` rg 'function debugLog' # Search for the definition of `jsonPrint` rg 'function jsonPrint'Length of output: 215
Script:
#!/bin/bash # Extract the implementation of `debugLog` rg -A 10 'export function debugLog' packages/debug-log/src/index.ts # Extract the implementation of `jsonPrint` rg -A 10 'export function jsonPrint' packages/debug-log/src/index.tsLength of output: 815
35-40: Review thedebugLogfunction.The
debugLogfunction formats and logs debug messages. Ensure that the formatting is consistent and that the function handles edge cases appropriately.Verification successful
The
debugLogfunction is implemented correctly and handles formatting consistently. ThegetCountfunction ensures unique, incrementing count values, and the test cases verify the expected output.
- The
debugLogfunction formats messages consistently.- The
getCountfunction increments correctly and returns a padded string.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the usage of `debugLog` across the project to ensure consistent formatting. # Test: Search for usages of `debugLog`. Expect: Consistent formatting. rg --type ts 'debugLog'Length of output: 544
Script:
#!/bin/bash # Retrieve more context lines around the usages of `debugLog` in `packages/debug-log/src/index.ts` rg --type ts 'debugLog' -A 3 -B 3Length of output: 2637
Script:
#!/bin/bash # Retrieve the implementation of the `getCount` function to ensure it increments correctly and returns a padded string as expected. rg --type ts 'function getCount'Length of output: 88
Script:
#!/bin/bash # Retrieve the full implementation of the `getCount` function from `packages/debug-log/src/index.ts`. rg --type ts 'function getCount' -A 5 -B 2Length of output: 450
42-50: Review thejsonPrintfunction.The
jsonPrintfunction is designed to print JSON in a formatted box. Verify that the JSON formatting is correct and that the function handles different types of inputs appropriately.
62-78: Review thejsonExpectfunction.The
jsonExpectfunction is used for asserting JSON structures against expected values and logging the differences. Ensure that the diffing and logging mechanisms are accurate and consider adding more comprehensive tests to cover edge cases.
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (2)
.yarn/patches/pretify-deep-diff-npm-1.0.1-587f0078e3.patchis excluded by!**/.yarn/**yarn.lockis excluded by!**/yarn.lock,!**/*.lock
Files selected for processing (24)
- package.json (1 hunks)
- packages/css-additional-types/.vscode/extensions.json (1 hunks)
- packages/css-additional-types/.vscode/launch.json (1 hunks)
- packages/css-additional-types/.vscode/settings.json (1 hunks)
- packages/css-additional-types/package.json (1 hunks)
- packages/css/.vscode/extensions.json (1 hunks)
- packages/css/.vscode/launch.json (1 hunks)
- packages/css/.vscode/settings.json (1 hunks)
- packages/css/package.json (1 hunks)
- packages/debug-log/.editorconfig (1 hunks)
- packages/debug-log/.vscode/extensions.json (1 hunks)
- packages/debug-log/.vscode/launch.json (1 hunks)
- packages/debug-log/.vscode/settings.json (1 hunks)
- packages/debug-log/README.md (1 hunks)
- packages/debug-log/eslint.config.js (1 hunks)
- packages/debug-log/package.json (1 hunks)
- packages/debug-log/src/index.ts (1 hunks)
- packages/debug-log/tsconfig.json (1 hunks)
- packages/debug-log/tsconfig.node.json (1 hunks)
- packages/debug-log/vite.config.ts (1 hunks)
- packages/transform-to-vanilla/.vscode/extensions.json (1 hunks)
- packages/transform-to-vanilla/.vscode/launch.json (1 hunks)
- packages/transform-to-vanilla/.vscode/settings.json (1 hunks)
- packages/transform-to-vanilla/package.json (1 hunks)
Files skipped from review due to trivial changes (2)
- packages/debug-log/.vscode/extensions.json
- packages/debug-log/tsconfig.json
Files skipped from review as they are similar to previous changes (20)
- package.json
- packages/css-additional-types/.vscode/extensions.json
- packages/css-additional-types/.vscode/launch.json
- packages/css-additional-types/.vscode/settings.json
- packages/css-additional-types/package.json
- packages/css/.vscode/extensions.json
- packages/css/.vscode/launch.json
- packages/css/.vscode/settings.json
- packages/debug-log/.editorconfig
- packages/debug-log/.vscode/launch.json
- packages/debug-log/.vscode/settings.json
- packages/debug-log/README.md
- packages/debug-log/eslint.config.js
- packages/debug-log/package.json
- packages/debug-log/src/index.ts
- packages/debug-log/tsconfig.node.json
- packages/debug-log/vite.config.ts
- packages/transform-to-vanilla/.vscode/extensions.json
- packages/transform-to-vanilla/.vscode/launch.json
- packages/transform-to-vanilla/.vscode/settings.json
Additional comments not posted (2)
packages/css/package.json (1)
29-29: Approved addition of@mincho/debug-logtodevDependencies.The addition of
@mincho/debug-logis consistent with the PR's objective to enhance debugging capabilities.Verify dependency compatibility and impact.
Ensure that the version specified (
workspace:^) is compatible with the existing project setup and does not introduce conflicts.Verification successful
Approved addition of
@mincho/debug-logtodevDependencies.The addition of
@mincho/debug-logis consistent with the PR's objective to enhance debugging capabilities. The usage ofworkspace:^ensures version consistency across the monorepo, and no conflicts or issues were found.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify compatibility and impact of adding `@mincho/debug-log`. # Test: Search for any potential conflicts or issues introduced by this new dependency. rg --type json -A 5 $'@mincho/debug-log'Length of output: 1860
packages/transform-to-vanilla/package.json (1)
48-48: Approved addition of@mincho/debug-logtodevDependencies.The addition of
@mincho/debug-logsupports the PR's goal to enhance debugging capabilities.Verify dependency compatibility and impact.
Ensure that the version specified (
workspace:^) is compatible with the existing project setup and does not introduce conflicts.Verification successful
Approved addition of
@mincho/debug-logtodevDependencies.The addition of
@mincho/debug-logsupports the PR's goal to enhance debugging capabilities. The dependency is consistently used across multiple packages within the project, and no conflicts were found.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify compatibility and impact of adding `@mincho/debug-log`. # Test: Search for any potential conflicts or issues introduced by this new dependency. rg --type json -A 5 $'@mincho/debug-log'Length of output: 1860
|
/fast-forward |
|
Triggered from #34 (comment) by @black7375. Trying to fast forward Target branch ( commit 9b79c35d58008bbd0dc7c06139db54edc3e1cc49 (HEAD -> main, origin/main, origin/HEAD)
Author: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Date: Mon Jul 15 09:31:11 2024 +0000
Chore(deps): Bump the npm_and_yarn group with 2 updates
Bumps the npm_and_yarn group with 2 updates: [braces](https://github.com/micromatch/braces) and [tar](https://github.com/isaacs/node-tar).
Updates `braces` from 3.0.2 to 3.0.3
- [Changelog](https://github.com/micromatch/braces/blob/master/CHANGELOG.md)
- [Commits](https://github.com/micromatch/braces/compare/3.0.2...3.0.3)
Updates `tar` from 6.2.0 to 6.2.1
- [Release notes](https://github.com/isaacs/node-tar/releases)
- [Changelog](https://github.com/isaacs/node-tar/blob/main/CHANGELOG.md)
- [Commits](https://github.com/isaacs/node-tar/compare/v6.2.0...v6.2.1)
---
updated-dependencies:
- dependency-name: braces
dependency-type: indirect
dependency-group: npm_and_yarn
- dependency-name: tar
dependency-type: indirect
dependency-group: npm_and_yarn
...
Signed-off-by: dependabot[bot] <support@github.com>Pull request ( commit cc6e3c6cfcee19f7d654b0389ac1e0076fbcfd22 (pull_request/debugging)
Author: alstjr7375 <alstjr7375@daum.net>
Date: Wed Jul 17 15:52:17 2024 +0900
Chore: Console debug package #33Fast forwarding $ git push origin cc6e3c6cfcee19f7d654b0389ac1e0076fbcfd22:main
To https://github.com/mincho-js/mincho.git
9b79c35..cc6e3c6 cc6e3c6cfcee19f7d654b0389ac1e0076fbcfd22 -> main |
Description
Configure a convenient debugging environment #33
Summary by CodeRabbit
New Features
@mincho/debug-logutility for simplified console debugging in JavaScript, now available in multiple packages.Documentation
debug-logutility.Chores