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

fix: Add ParseResultIp to main.js exports #157

Merged
merged 1 commit into from Mar 4, 2024

Conversation

OiYouYeahYou
Copy link
Contributor

Sorry for the triviality of this. It seems you missed passing an export in your entry point

@jhnns
Copy link
Member

jhnns commented Mar 4, 2024

Oops. Thank you 😁

(Funny that after all these years no one noticed this...)

@jhnns jhnns changed the title Add ParseResultIp to main.js exports fix: Add ParseResultIp to main.js exports Mar 4, 2024
@jhnns jhnns merged commit b5b0177 into peerigon:main Mar 4, 2024
3 checks passed
github-actions bot pushed a commit that referenced this pull request Mar 4, 2024
## [8.0.2](v8.0.1...v8.0.2) (2024-03-04)

### Bug Fixes

* Add `ParseResultIp` to `main.js` exports ([#157](#157)) ([b5b0177](b5b0177))
Copy link

github-actions bot commented Mar 4, 2024

🎉 This PR is included in version 8.0.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

@OiYouYeahYou
Copy link
Contributor Author

No problem, thank you for merging.

I have my suspicions the only reason I noticed is because I'm using the import as a namespace.

@OiYouYeahYou OiYouYeahYou deleted the add-exports branch March 5, 2024 22:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants