fix: README.md misleading dev to use wrong import code on while working with ES6 Import. #916
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context:
import * as HoneyBadger from '@honeybadger-io/js'
as indicated in the documentation using nodejs + TypeScript results in errors such as 'configure' is not a function.What really works in a nodejs + TypeScript context is using:
import HoneyBadger from '@honeybadger-io/js'
Status
READY
Description
A Change in the README.MD file to make it clear which is the right import statement to use while using ES6 imports + TypeScript
Todos