ci(automate): fix automate dependencies error #2428
Conversation
WalkthroughThis pull request includes modifications to multiple Changes
Possibly related PRs
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 using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
[e2e-test-warn] The title of the Pull request should look like "fix(vue-renderless): [action-menu, alert] fix xxx bug". Please make sure you've read our contributing guide |
zzcr
changed the title
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Outside diff range and nitpick comments (2)
packages/vue/src/sticky/package.json (1)
Line range hint
1-22: Document dependency changes in package.json.Consider adding a comment in the package.json description field or updating the component's documentation to explain why mobile theming is no longer needed. This will help future maintainers understand the rationale behind the dependency changes.
packages/vue/src/loading/package.json (1)
21-22: Consider updating documentation for icon usage.If the loading component uses icons, please ensure the component's documentation reflects this new dependency and describes which icons are available/used.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (11)
- internals/automate/src/add-dependencies.ts (3 hunks)
- packages/vue/src/base-select/package.json (1 hunks)
- packages/vue/src/config-provider/package.json (1 hunks)
- packages/vue/src/dialog-select/package.json (1 hunks)
- packages/vue/src/image/package.json (1 hunks)
- packages/vue/src/load-list/package.json (1 hunks)
- packages/vue/src/loading/package.json (1 hunks)
- packages/vue/src/sticky/package.json (1 hunks)
- packages/vue/src/switch/package.json (1 hunks)
- packages/vue/src/time-range/package.json (1 hunks)
- packages/vue/src/upload/package.json (1 hunks)
🔇 Additional comments (18)
packages/vue/src/config-provider/package.json (2)
18-18: LGTM! Removed circular dependency.Good cleanup by removing the self-dependency
@opentiny/vue-config-provider. Circular dependencies can cause resolution issues and are generally considered an anti-pattern.
17-19: Verify the impact of removing self-dependency.Let's ensure that removing the self-dependency doesn't break any functionality.
✅ Verification successful
Let me try another verification approach since the previous commands had issues with the file type.
Removing self-dependency is safe
Based on the verification results:
- The component only depends on
@opentiny/vue-commonand@opentiny/vue-theme- No circular dependencies or self-imports of
@opentiny/vue-config-providerfound in the component's source files- The only reference to the package name is in tests, which is a valid external import
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Check for any internal usage of the config-provider within itself # Test 1: Look for imports of config-provider within its own directory echo "Checking for internal usage of config-provider..." rg -t ts -t vue "from ['|\"]@opentiny/vue-config-provider" packages/vue/src/config-provider/ # Test 2: Check if any files reference the package name echo "Checking for package name references..." rg "@opentiny/vue-config-provider" packages/vue/src/config-provider/ --type ts --type vue # Test 3: Look for potential circular dependency patterns echo "Checking for circular dependency patterns..." ast-grep --pattern 'import { $$$ } from "@opentiny/vue-config-provider"'Length of output: 614
Script:
#!/bin/bash # Let's check for any self-references using more reliable commands # Check all files in the config-provider directory echo "Files in config-provider directory:" fd . packages/vue/src/config-provider/ # Look for any imports or requires in the directory echo -e "\nChecking for any imports/requires:" rg "require|import" packages/vue/src/config-provider/ # Check package.json dependencies before removal echo -e "\nChecking package.json:" cat packages/vue/src/config-provider/package.jsonLength of output: 3114
packages/vue/src/sticky/package.json (1)
8-11: Verify mobile theme dependency removal.The removal of
@opentiny/vue-theme-mobiledependency might affect mobile-specific styling. Please ensure that:
- The sticky component doesn't require mobile-specific theming
- Any mobile-specific styles are now handled elsewhere
✅ Verification successful
Removal of vue-theme-mobile dependency is safe
The sticky component only uses the base theme package (
@opentiny/vue-theme) for its styles throughsticky/index.less. While there is a mobile-first template import pattern, it doesn't specifically depend on the mobile theme package. The removal of@opentiny/vue-theme-mobiledependency appears to be a safe cleanup.
packages/vue/src/sticky/src/pc.vue: Uses base theme import@opentiny/vue-theme/sticky/index.lesspackages/vue/src/sticky/src/index.ts: Uses virtual template with mobile-first pattern but no direct mobile theme dependency🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Check if the sticky component has any mobile-specific theme usage rg -l "theme.*mobile" packages/vue/src/sticky/Length of output: 48
Script:
#!/bin/bash # Let's check for any mobile-specific styles or theme references in the sticky component rg -i "mobile|theme" packages/vue/src/sticky/ -A 3 # Also check for any theme imports or configurations ast-grep --pattern 'import $_ from "@opentiny/vue-theme$_"' # Check if there are any mobile-specific class names or styles rg -i "class.*mobile|style.*mobile" packages/vue/src/sticky/Length of output: 938
packages/vue/src/load-list/package.json (2)
11-11: Consider updating documentation for i18n support.If this component now supports internationalization, it would be helpful to document this capability in the component's documentation.
Let's check if documentation exists and needs updating:
#!/bin/bash # Look for documentation files fd -t f "README" "packages/vue/src/load-list/"
11-11: Verify the usage of newly added locale dependency.The addition of
@opentiny/vue-localesuggests internationalization support for this component.Let's verify if the locale dependency is being utilized:
✅ Verification successful
Locale dependency is properly utilized in the component
The
@opentiny/vue-localedependency is correctly used in the component's implementation:
- Imported and used via
t()function for internationalization- Applied to default text properties:
errorText,loadingText, andfinishedText- Follows the standard i18n pattern with
ui.loadList.*translation keys🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Check if the component actually uses the locale dependency rg -l "import.*@opentiny/vue-locale" "packages/vue/src/load-list/" # Look for typical i18n usage patterns rg "t\(['\"](.*?)['\"]\)" "packages/vue/src/load-list/"Length of output: 138
Script:
#!/bin/bash # Check for locale imports with different patterns rg -l "@opentiny/vue-locale" "packages/vue/src/load-list/" # Check for i18n related code patterns rg -l "useLocale|createI18n|i18n\." "packages/vue/src/load-list/" # Look at the component's source files to understand the implementation fd -e vue -e js . "packages/vue/src/load-list/" -x cat {}Length of output: 1963
Script:
#!/bin/bash # Let's check the index.ts file that shows locale import cat "packages/vue/src/load-list/src/index.ts" # Check the renderless implementation for locale usage rg -l "@opentiny/vue-locale" "packages/vue/src/renderless/load-list/" cat "packages/vue/src/renderless/load-list/vue.ts"Length of output: 1280
packages/vue/src/image/package.json (2)
21-22: LGTM! Dependency declaration follows project conventions.The new dependency follows the established patterns:
- Uses the workspace protocol with consistent version specifier
- Maintains proper alphabetical ordering
21-22: Verify the icon dependency usage in the image component.The addition of
@opentiny/vue-iconas a dependency is consistent with similar updates across other components in this PR.Let's verify if this dependency is actually used in the image component:
✅ Verification successful
Icon dependency is correctly added and used in the image component
The
@opentiny/vue-icondependency is justified as the component uses theiconImageErroricon from this package:
- Imports
iconImageErrorfrom '@opentiny/vue-icon'- Uses it as
TinyIconImageErrorcomponent in the error state template- Registers it in components section:
TinyIconImageError: iconImageError()🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Check if the image component uses icons from @opentiny/vue-icon # Test: Search for icon imports or usage in the image component rg -t ts -t vue "@opentiny/vue-icon" "packages/vue/src/image/"Length of output: 88
Script:
#!/bin/bash # Let's try a different approach to search for icon-related code in the image component # First, let's find the main component file fd -t f "index" "packages/vue/src/image" --exec cat {} # Also search for any icon-related terms without specific package rg -l "icon|Icon" "packages/vue/src/image"Length of output: 2901
Script:
#!/bin/bash # Let's examine the pc.vue file which seems to contain icon-related code cat "packages/vue/src/image/src/pc.vue"Length of output: 2564
packages/vue/src/switch/package.json (2)
22-22: LGTM on dependency version syntax.The use of
workspace:~for version specifier is consistent with other dependencies in the package.
21-22: Verify the necessity of @opentiny/vue-icon dependency.Let's verify that this dependency is actually used in the switch component code.
✅ Verification successful
Let's gather more information about how the icon dependency is used in the identified files.
The @opentiny/vue-icon dependency is correctly added and actively used
The switch component legitimately uses the icon dependency:
- In
pc.vue: Imports and usesIconLoadingShadowfor loading state- In tests: Uses
IconArrowLeftandIconArrowRightfor testing icon slots functionality🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Search for icon imports or usage in switch component echo "Checking for icon imports in switch component..." rg -l "import.*@opentiny/vue-icon" "packages/vue/src/switch" echo "Checking for icon usage patterns..." ast-grep --pattern 'Icon' "packages/vue/src/switch"Length of output: 383
Script:
#!/bin/bash # Check the actual icon imports and usage in the files echo "Checking icon imports and usage in pc.vue..." rg "import.*@opentiny/vue-icon" -A 5 "packages/vue/src/switch/src/pc.vue" rg "Icon" -A 5 "packages/vue/src/switch/src/pc.vue" echo -e "\nChecking icon imports and usage in switch.test.tsx..." rg "import.*@opentiny/vue-icon" -A 5 "packages/vue/src/switch/__tests__/switch.test.tsx" rg "Icon" -A 5 "packages/vue/src/switch/__tests__/switch.test.tsx"Length of output: 1679
packages/vue/src/loading/package.json (1)
21-22: Verify the necessity of @opentiny/vue-icon dependency.Let's verify if the loading component actually uses icons from this package.
✅ Verification successful
Let's check the content of pc.vue to understand how icons are used in the loading component.
The @opentiny/vue-icon dependency is correctly added and necessary
The loading component uses the
iconLoadingShadowcomponent from@opentiny/vue-iconpackage as its default loading spinner. This is evidenced by:
- The import statement:
import { iconLoadingShadow } from '@opentiny/vue-icon'- Component registration:
TinyIconLoadingShadow: iconLoadingShadow()- Usage in template:
<tiny-icon-loading-shadow v-else class="circular"></tiny-icon-loading-shadow>🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Search for icon usage in the loading component echo "Searching for icon imports and usage in loading component..." rg -l "vue-icon|Icon" "packages/vue/src/loading" # Search for loading component implementation to understand icon usage ast-grep --pattern 'import { $_ } from "@opentiny/vue-icon"'Length of output: 316
Script:
#!/bin/bash # Check the content of pc.vue for icon usage echo "Checking pc.vue for icon imports and usage..." cat "packages/vue/src/loading/src/pc.vue" # Also check for any icon-related props or components ast-grep --pattern 'import { $_ } from "@opentiny/vue-icon"' "packages/vue/src/loading/src/pc.vue"Length of output: 1990
packages/vue/src/time-range/package.json (1)
21-22: Verify the necessity of @opentiny/vue-button dependency.The addition of
@opentiny/vue-buttonappears to be part of the automated dependency detection. Let's verify if this dependency is actually used in the time-range component.✅ Verification successful
@opentiny/vue-button dependency is correctly required
The time-range component uses the Button component (
tiny-button) in its template for both cancel and confirm actions. The dependency is imported asButton from '@opentiny/vue-button'and registered asTinyButtonin the components section.Specific usage found in pc.vue:
- Import statement:
import Button from '@opentiny/vue-button'- Component registration:
components: { TimeSpinner, TinyButton: Button }- Template usage:
- Cancel button:
<tiny-button class="tiny-time-range-picker__btn cancel">- Confirm button:
<tiny-button size="small">🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Check if the time-range component actually uses the button component # Search for button imports or usage in time-range component echo "Checking for button component usage in time-range..." rg -l --type ts --type vue "@opentiny/vue-button|TinyButton" "packages/vue/src/time-range" # Check if the dependency was automatically added by the dependency detection tool echo "Checking automated dependency addition..." rg -l "addDependencies|updateDependencies" "packages/vue/scripts"Length of output: 453
Script:
#!/bin/bash # Let's try a different approach to check for button usage # First, let's find the main component file echo "Finding time-range component files..." fd . "packages/vue/src/time-range" -t f -e ts -e js -e vue # Then let's search for Button-related content with proper file type handling echo "Checking for Button usage..." rg -t js -t typescript -t html "Button|button" "packages/vue/src/time-range" # Let's also check package.json to understand the context better echo "Checking package.json content..." cat packages/vue/src/time-range/package.jsonLength of output: 1180
Script:
#!/bin/bash # Let's check the actual content of the component files echo "Checking content of pc.vue..." cat "packages/vue/src/time-range/src/pc.vue" echo "Checking content of index.ts..." cat "packages/vue/src/time-range/index.ts"Length of output: 5603
packages/vue/src/upload/package.json (2)
22-23: LGTM! Icon dependency addition is consistent.The addition of
@opentiny/vue-iconas a workspace dependency aligns with the standardization across other packages.
23-23: Verify icon usage in the upload component.Let's verify that this dependency is actually used in the upload component code.
✅ Verification successful
Let me check the actual usage of icons in the mobile-first.vue file to verify this dependency.
Icon dependency is correctly used in the upload component
The
@opentiny/vue-icondependency is actively used inmobile-first.vuewhere it imports and uses theiconHelpCirclecomponent, confirming this is a necessary dependency.🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Check if the upload component actually uses icons from @opentiny/vue-icon # Search for icon imports or usage in the upload component echo "Checking for icon imports and usage in upload component..." rg -l "vue-icon|Icon" packages/vue/src/upload/Length of output: 257
Script:
#!/bin/bash # Check the actual icon usage in mobile-first.vue echo "Checking icon imports and usage in mobile-first.vue..." rg "(@opentiny/vue-icon|Icon)" -A 2 packages/vue/src/upload/src/mobile-first.vueLength of output: 391
packages/vue/src/dialog-select/package.json (1)
24-25: Verify the necessity of @opentiny/vue-icon dependency.The addition follows the correct workspace dependency format, but let's verify if the dialog-select component actually uses icons.
✅ Verification successful
@opentiny/vue-icon dependency is correctly required
The dialog-select component actively uses the icon component:
- Imports
iconSearchfrom '@opentiny/vue-icon'- Uses
<tiny-icon-search>component in the template- Registers
TinyIconSearchin components usingiconSearch()🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Check if the dialog-select component actually uses the icon component # Expected: Find imports or uses of icons in the dialog-select component code # Search for icon imports or usage in dialog-select source files echo "Checking for icon usage in dialog-select component:" rg -l "icon" "packages/vue/src/dialog-select" --type ts --type vue # Check for specific icon component imports echo -e "\nChecking for specific icon imports:" rg -l "@opentiny/vue-icon" "packages/vue/src/dialog-select" --type ts --type vueLength of output: 399
Script:
#!/bin/bash # Let's try a different approach using fd to find files first, then search within them # Find all relevant files echo "Files in dialog-select directory:" fd . "packages/vue/src/dialog-select" -t f echo -e "\nChecking for icon usage in these files:" fd . "packages/vue/src/dialog-select" -t f -x rg -l "icon" {} \; echo -e "\nChecking for specific icon imports:" fd . "packages/vue/src/dialog-select" -t f -x rg -l "@opentiny/vue-icon" {} \; # Let's also check the actual content where icons might be used echo -e "\nDetailed icon-related content:" fd . "packages/vue/src/dialog-select" -t f -x rg "icon" -C 2 {} \;Length of output: 1572
packages/vue/src/base-select/package.json (2)
30-30: LGTM on dependency version format.The
workspace:~version specifier is correct for internal package dependencies.
29-30: Verify the usage of @opentiny/vue-tree in base-select component.Let's verify that this dependency is actually being used in the base-select component's code.
✅ Verification successful
The tree component dependency is correctly used and required
The verification confirms that the base-select component directly imports and uses the tree component in mobile-first.vue:
- Imports
TinyTreefrom '@opentiny/vue-tree'- Uses
<tiny-tree>component in the template whenrenderType === 'tree'- Implements tree-specific functionality like
filterMethod,nodeCheckClick, etc.🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Check if base-select actually imports or uses the tree component # Test 1: Look for direct imports of tree component echo "Checking for direct imports of tree component..." rg -l "from ['\"]\@opentiny\/vue-tree['\"]" packages/vue/src/base-select/ # Test 2: Look for tree-related component usage in template echo "Checking for tree component usage in templates..." rg -l "<tiny-tree|TinyTree" packages/vue/src/base-select/ # Test 3: Check if this might create circular dependencies echo "Checking if tree component depends back on base-select..." rg -l "from ['\"]\@opentiny\/vue-base-select['\"]" packages/vue/src/tree/Length of output: 835
Script:
#!/bin/bash # Let's fix the regex syntax and try again # Test 1: Look for direct imports of tree component echo "Checking for direct imports of tree component..." rg -l "from ['\"]@opentiny/vue-tree['\"]" packages/vue/src/base-select/ # Test 2: Look for any references to tree component echo "Checking for any tree references..." rg -C 3 "tree" packages/vue/src/base-select/src/mobile-first.vue # Test 3: Check if tree component depends back on base-select echo "Checking for potential circular dependencies..." rg -l "from ['\"]@opentiny/vue-base-select['\"]" packages/vue/src/tree/ # Test 4: Let's check the actual implementation where tree is used echo "Checking the implementation in mobile-first.vue..." cat packages/vue/src/base-select/src/mobile-first.vueLength of output: 28045
internals/automate/src/add-dependencies.ts (2)
30-30: LGTM: Adding newline improves file format consistency.Adding a newline character at the end of JSON files follows best practices and improves version control diff readability.
76-77: 🛠️ Refactor suggestionVerify directory rename and consider refactoring.
The change from 'chart' to 'huicharts' suggests a component directory rename. Please verify this is intentional and all related changes are made.
The code structure is duplicated. Consider refactoring to avoid repetition:
Let's verify the directory rename:
#!/bin/bash # Description: Check references to the old 'chart' directory # Expected: No references to the old directory name should remain echo "Checking for remaining references to 'chart' directory:" rg -i "chart" --type ts --type vueConsider this refactoring to reduce code duplication:
-scanDir(root, 'dir').then((dirs) => { - dirs.forEach((dir) => addComponentDepencies(dir, root)) -}) - -scanDir(path.join(root, 'huicharts'), 'dir').then((dirs) => { - dirs.forEach((dir) => addComponentDepencies(dir, path.join(root, 'huicharts'))) -}) +const dirsToScan = [ + { path: root, base: root }, + { path: path.join(root, 'huicharts'), base: path.join(root, 'huicharts') } +] + +Promise.all( + dirsToScan.map(async ({ path: scanPath, base }) => { + const dirs = await scanDir(scanPath, 'dir') + return dirs.forEach((dir) => addComponentDepencies(dir, base)) + }) +)
| "@opentiny/vue-theme": "workspace:~", | ||
| "@opentiny/vue-button": "workspace:~" |
There was a problem hiding this comment.
💡 Codebase verification
Version inconsistencies found in workspace dependencies
Two packages are using non-workspace versions which should be updated to maintain consistency:
packages/vue/src/huicharts/huicharts-core/package.json:@opentiny/huichartsuses version1.0.1packages/vue/src/fluent-editor/package.json:@opentiny/fluent-editoruses version~3.20.0
The remaining 1,228 @opentiny dependencies correctly use workspace:~ versioning.
🔗 Analysis chain
Verify workspace version consistency.
The workspace:~ version specifier is consistent with other dependencies in this file and aligns with the pattern seen across other package updates.
Let me gather more specific information about the outliers to provide a complete verification.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify consistency of workspace:~ version usage across package.json files
# Check if all @opentiny dependencies use workspace:~ version
echo "Checking version consistency across package.json files..."
fd package.json packages/vue/src -x grep -l "workspace:~" {} \; | \
xargs jq -r '.dependencies | select(.) | to_entries[] | select(.key | startswith("@opentiny")) | .value' | \
sort | uniq -c
Length of output: 367
Script:
#!/bin/bash
# Find the specific package.json files with non-workspace versions
echo "Files with version 1.0.1:"
fd package.json packages/vue/src -x sh -c 'if jq -e ".dependencies | select(.) | to_entries[] | select(.key | startswith(\"@opentiny\")) | select(.value == \"1.0.1\")" {} > /dev/null; then echo {}; fi'
echo -e "\nFiles with version ~3.20.0:"
fd package.json packages/vue/src -x sh -c 'if jq -e ".dependencies | select(.) | to_entries[] | select(.key | startswith(\"@opentiny\")) | select(.value == \"~3.20.0\")" {} > /dev/null; then echo {}; fi'
echo -e "\nShowing the specific dependencies with non-workspace versions:"
fd package.json packages/vue/src -x sh -c 'if jq -e ".dependencies | select(.) | to_entries[] | select(.key | startswith(\"@opentiny\")) | select(.value != \"workspace:~\")" {} > /dev/null; then echo "=== {}:"; jq ".dependencies | to_entries[] | select(.key | startswith(\"@opentiny\")) | select(.value != \"workspace:~\")" {}; fi'
Length of output: 1340
| @@ -55,7 +55,7 @@ async function addComponentDepencies(component, dir) { | |||
| const allFiles = await fg(['**/*.ts', '**/*.vue'], { | |||
| dot: true, | |||
| cwd: componentPath, | |||
| ignore: ['**/node_modules', '__test__'] | |||
| ignore: ['**/node_modules', '__test__', '__tests__'] | |||
There was a problem hiding this comment.
💡 Codebase verification
Test directory naming convention needs standardization
The codebase shows inconsistent test directory naming patterns in the Vue package:
- Most components (54) use
__tests__(double underscore) - Some components (11) use
__test__(single underscore)
This inconsistency should be standardized to __tests__ as it's:
- The more commonly used pattern in this codebase
- The more widely adopted convention in the JavaScript/TypeScript ecosystem
Components using __test__ that need updating:
- action-menu
- collapse-item
- collapse
- divider
- dropdown
- fullscreen
- pager
- tooltip
- tree
- user-contact
- user-head
🔗 Analysis chain
Verify test directory naming consistency across the codebase.
While ignoring both __test__ and __tests__ is more comprehensive, having both patterns might indicate inconsistent test directory naming conventions.
Let's check the test directory naming patterns:
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check for inconsistent test directory naming patterns
# Expected: All test directories should follow the same naming convention
echo "Directories with '__test__' pattern:"
fd -t d "__test__$"
echo -e "\nDirectories with '__tests__' pattern:"
fd -t d "__tests__$"
Length of output: 283
Script:
#!/bin/bash
# Let's try a different approach to find test directories
# Using find command which is more reliable for this case
echo "Directories with '__test__' pattern:"
find . -type d -name "__test__" -not -path "*/node_modules/*" -not -path "*/\.*"
echo -e "\nDirectories with '__tests__' pattern:"
find . -type d -name "__tests__" -not -path "*/node_modules/*" -not -path "*/\.*"
# Also let's check for any test files that might indicate the convention
echo -e "\nFiles in directories containing 'test':"
find . -type d -name "*test*" -not -path "*/node_modules/*" -not -path "*/\.*" | while read dir; do
echo "Directory: $dir"
ls -1 "$dir" 2>/dev/null || true
done
Length of output: 16515
PR
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information
Summary by CodeRabbit
Release Notes
New Features
@opentiny/vue-treein@opentiny/vue-base-select@opentiny/vue-iconin@opentiny/vue-dialog-select,@opentiny/vue-image,@opentiny/vue-loading,@opentiny/vue-switch, and@opentiny/vue-upload@opentiny/vue-localein@opentiny/vue-load-list@opentiny/vue-buttonin@opentiny/vue-time-range@opentiny/vue-theme-mobilefrom@opentiny/vue-sticky, reducing dependencies.Bug Fixes