Fix test capturing return value from void function

[Copilot]

Addresses review feedback on PR #214: test case was capturing the return value of execute(), which is declared as void.

Changes

• Modified test case6 in TextFieldSelectedFocusMoveUseCase.test.ts to not capture the return value
• Aligned with the pattern used by other test cases in the file

Before:

it("execute test case6 - returns undefined", () => {
    const textField = new TextField();
    textField.text = "Test";
    textField.selectIndex = 2;
    
    const result = execute(textField);
    
    expect(result).toBeUndefined();
});

After:

it("execute test case6 - handles normal selectIndex", () => {
    const textField = new TextField();
    textField.text = "Test";
    textField.selectIndex = 2;
    
    expect(() => {
        execute(textField);
    }).not.toThrow();
});

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Pull Request Overview

This PR updates test assertions and removes unnecessary peer: true flags from package-lock.json dependencies.

• Test case 6 refactored to use toThrow() assertion instead of checking toBeUndefined()
• Removed peer: true flags from multiple npm package entries in package-lock.json

Reviewed Changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

File	Description
packages/text/src/TextField/usecase/TextFieldSelectedFocusMoveUseCase.test.ts	Updated test case 6 to verify the function doesn't throw instead of checking for undefined return value, improving test clarity
package-lock.json	Removed peer: true flags from various package entries to correct dependency metadata

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.