-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Throw a more detailed error message on require of ESM modules #2105
Comments
Nice idea! Do you want to pair on fixing it? You can book me at https://calendly.com/mattwynne |
I'd love to, but I've got to dig up some time. I'll schedule something later in the week. |
In a similar vein it would make sense to emit a warning when |
The error message is not a cucumber one. For more details and fix see: #2248 (comment) |
@Izhaki I'm aware of that, but it is triggered by Cucumber trying to load code and will frequently be due to misconfguration, so if we can surface that in a more useful way I think that's worthwhile. |
This issue now has a pull request so let's continue discussion in the thread of that PR. |
🤔 What's the problem you've observed?
I was stumped for about a full day by using the require directive in my configuration when I should have been using the import directive. Let's try to make the error message that the user sees more effective in pointing the user in the correct direction.
✨ Do you have a proposal for making it better?
Current error message
If we can catch that error we can throw this in it's place.
Maybe even go so far as to point out the exact code change needed?
The text was updated successfully, but these errors were encountered: