[Antreesy]

Replace NcActionInput with NcPopover + NcTextField

• NcActionInput imports NcPasswordField, NcDateTimePickerNative and lazy NcColorPicker, NcDateTimePicker and NcSelect
  • All those come bundled with library that may or may not use FilePicker (incl. ~100 date-fns locales in dist)
• The "New folder" menu only needs a text field
  • Use NcPopover with NcButton trigger and NcTextField in a form, so Enter and the trailing arrow button submit
  • Keep the previous layout and spacing of NcActions with NcActionInput (folder icon aligned with the label, same paddings)
  • Reuse the existing translation strings

Screenshots:

Before	After
--	See icon alignment

Net effect (bruteforcesettings app):

bruteforcesettings js/ (no .map / LICENSE)	Before (HEAD)	After	Diff
Total size	2,437 KB	1,248 KB	−1,188 KB (−49%)
Number of files	102	6	−96 (date-fns locales)
bruteforcesettings-main.js	979 KB	876 KB	−103 KB
FilePicker chunk	341 KB	329 KB	−11 KB
NcColorPicker / NcDateTimePicker chunks	2	0	−2

🤖 AI (if applicable)

• The content of this PR was partly or fully generated using AI (ClaudeCode:claude-opus-5-5)

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 61.74%. Comparing base (c78bf13) to head (6b6e633).
⚠️ Report is 4 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2690   +/-   ##
=======================================
  Coverage   61.74%   61.74%           
=======================================
  Files          15       15           
  Lines         481      481           
  Branches      104      104           
=======================================
  Hits          297      297           
  Misses        165      165           
  Partials       19       19           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[susnux]

This seems like the wrong kind of optimization, instead of work around the symptoms the root cause should be fixed.
This is normal usage of the component for exact the use case it is expected to be used.
If there is a performance problem, then this should be fixed in the actions component directly

[Antreesy]

If there is a performance problem, then this should be fixed in the actions component directly

I'd say it's more a bundling / tree-shaking problem, and specifically this one can't be solved without breaking changes.

Under the hood, you will get the same NcPopover and NcTextfield like in this PR, but because of multifunctional nature of NcActions* you will get an extra logic and async chunks on top (color picker, date picker, e.t.c.).
Unless we introduce light version of NcActionInput, there won't be any gain

This is normal usage of the component for exact the use case it is expected to be used.

And it may be acceptable for downstream app, but not for the library. IMO here we can and should trade off some complex boilerplate for final size.

[susnux]

And it may be acceptable for downstream app, but not for the library. IMO here we can and should trade off some complex boilerplate for final size.

It should not be acceptable anywhere. The component then must be fixed to only use what is needed.

---

I mean I guess for the short term this is "ok" (meaning this PR I guess we can apply!).

But this is not a fix, its just bandaid because of broken design of the component underneath.
I see this quite often that we apply "fixes" which are just workarounds and the real problem is not solved. In the end what is the reason to have the actions then anyways if you always have to workaround it?
All apps and libraries have then again applying similar workarounds instead of us fixing it properly by providing a solution for the root cause.