Vite: Fix lodash imports with optimizeDeps

[thtliife]

lodash imports using the file extension cause an error in vite unless included in the optimizeDeps.include array in the viteFinal config for storybook.

Closes: #21527

What I did

This commit replaces lodash imports to exclude the file extension.

eg.

before: import camelCase from 'lodash/camelCase.js';

after: import camelCase from 'lodash/camelCase';

How to test

Checklist

• Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests)
• Make sure to add/update documentation regarding your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Maintainers

• If this PR should be tested against many or all sandboxes,
  make sure to add the ci:merged or ci:daily GH label to it.
• Make sure this PR contains one of the labels below.

["cleanup", "BREAKING CHANGE", "feature request", "bug", "documentation", "maintenance", "dependencies", "other"]

[JReinhold]

There was a PR specifically for adding .js extensions to lodash by @IanVS, because it fixed an issue. I'm not sure it is straight forward to just remove them again.

#20443

[ndelangen]

@thtliife I think my PR here: #21535 supersedes this PR.
Removing the extensions is not desired, I think.

[thtliife]

@thtliife I think my PR here: #21535 supersedes this PR.

Removing the extensions is not desired, I think.

Fair enough. I know that vite seems to treat paths with an extension as if they are project files, that's why I took the route of removing them.
I have closed the PR though and guess I'll stick to manually adding deps to the optimzedDeps array to keep my storybooks working 🙂

[IanVS]

@thtliife thanks for the contribution. We'll get it fixed for sure, you shouldn't have to change your optimizedDeps array. Currently, rc.1 does not have this bug, so feel free to update to that version, unless you need yarn pnp support, then you'll need to update your array as you mention and wait for a fix to be released.

[thtliife]

@IanVS Ahh nice, glad it's fixed already 🙂

I WISH I needed yarnpnp support...
My project has too many other deps that aren't pnp compatible...
Not many other repos are as responsive as you guys 🤪