Fix constructNow import paths

[fturmel]

Introduced by #3731. None of the internal imports go through the root index that re-exports all functions.

Although maybe this is not an issue anymore? The browser tests on GitHub actions are not timing out like they used to (see #3677) since the Vitest 1.3 upgrade.

If this can still cause problems, maybe the root index (and fp index) could be removed from the repo and only generated when publishing to the npm registry?

[kossnocorp]

Introduced by #3731. None of the internal imports go through the root index that re-exports all functions.

Thank you so much. I used auto imports and missed it 🤦‍♂️ I have to find or write an ESLint plugin to prevent it.

Although maybe this is not an issue anymore? The browser tests on GitHub actions are not timing out like they used to (see #3677) since the Vitest 1.3 upgrade.

I had to fix browser tests, and it seems Vitest was choking because of the number of tests. See: vitest-dev/vitest#5382

If this can still cause problems, maybe the root index (and fp index) could be removed from the repo and only generated when publishing to the npm registry?

That's another way to approach it. I like it even more than linting. I'll look into that!

---

PS: I tried to contact you via email. Not sure if you saw my messages. Can you please open a GitHub Sponsors account? I love your work so much and would like to support it.

[kossnocorp]

🙏 thank you