Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐛 filenames like component.utils.ts are not resolved properly and breaks build #346

Closed
w0ofy opened this issue Aug 14, 2022 · 1 comment
Labels

Comments

@w0ofy
Copy link

w0ofy commented Aug 14, 2022

What is this

🐛 bug report

File names that include a . to separate words, other than the file-extension itself, are not being resolved properly and as a result, the build process exits with a thrown error... since the file name it resolved to, doesn't export (in this case) the expected "utility" functions.

// input file name
component.utils.ts

// resolved file name
component.ts

// error looks like
Error: 'sortNodes' is not exported by src/component.tsx, imported by src/component.tsx

In the above error snippet, of course src/component.tsx doesn't export sortNodes. sortNodes utility function lives inside src/component.utils.ts and is imported into the actual component e.g.

// src/component.tsx

import { sortNodes } from './component.utils.ts`;

const MyComponent = () => (
  // ...
)

export { MyComponent };

Potential root cause

I think this #345. Looks like the logic in this PR doesn't consider that file names can include multiple instances of .

Hope this is clear enough. Let me know if I can be of more help here 👍

@github-actions
Copy link

🎉 This issue has been resolved in version 4.9.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant