Update del to v6.1.1 for security improvements

[ram-ui-dev]

Summary

Updates the del dependency from v4.1.1 to v6.1.1, bringing significant security improvements and updated dependencies while maintaining CommonJS compatibility.

Motivation

• Eliminates dependency on the vulnerable glob package (replaced with fast-glob)
• Updates globby from v6.1.0 to v11.0.1 (5 major versions)
• Addresses security concerns from outdated dependencies
• Improves performance with modern fast-glob implementation

Changes Made

1. Updated Dependencies

• del: ^4.1.1 → ^6.1.1
  • Brings globby@11.0.1 (uses fast-glob instead of glob)
  • Updates rimraf to v3
  • Adds graceful-fs for better filesystem reliability

2. Updated Error Handling

• Modified error message regex to match del@6.x format
• Changed "files/folders" to "files/directories" in error detection
• Added TypeScript type assertion for better type safety

3. Fixed Tests

• Updated two tests that delete files outside the output directory
• Added explicit dangerouslyAllowCleanPatternsOutsideProject: true option
• Required due to stricter path validation in del@6.x

4. Fixed ESLint Error (Bonus)

• Removed .js extension from jest.config import in wallaby.config.js
• Fixes import/extensions ESLint rule violation
• This was a pre-existing error on master that blocked pre-push hooks

Why Not del@7.x or del@8.x?

• del@7.0.0+ are pure ESM modules
• Current project uses CommonJS with Jest 24
• Upgrading to ESM would require converting entire project to ESM, upgrading Jest to v29+, and potential breaking changes for users
• del@6.1.1 is the optimal choice: Last CommonJS-compatible version with modern dependencies

Test Results

✅ All 42 tests passing (100%)
✅ Build successful
✅ TypeScript compilation successful

Breaking Changes

None - This is a drop-in replacement with the same API.

Checklist

• Tests pass locally
• Build succeeds
• No breaking changes to public API
• Updated error handling for del@6.x compatibility
• All existing functionality preserved

[nade33]

@johnagan this PR will fix the issue raised here #209