Skip to content

Revert serial #110

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

Merged
merged 3 commits into from
Sep 12, 2024
Merged

Revert serial #110

merged 3 commits into from
Sep 12, 2024

Conversation

Hunter275
Copy link
Member

Revert serial

@Hunter275 Hunter275 merged commit d6f8a0b into meshtastic:master Sep 12, 2024
3 checks passed
@Hunter275 Hunter275 deleted the revert-serial branch September 12, 2024 17:44
@benbrown
Copy link
Contributor

I am learning from reading the commit history -- why did this happen?

@nmaq-dev
Copy link

I have the same question! Why???

I've spent the last few hours trying to figure out how to accomplish this.

I ran across this issue in the python code meshtastic/python#74 which brought me here. I had looked in this repo for anything that was server-attached instead of browser-attached.

@benbrown
Copy link
Contributor

@nmaq-dev The reason is that bundling the node dependencies causes issues when used in a browser unless you do extra build steps yourself which is a recipe for pain. I have some PRs open around this, but I think the likely path forward will be a separate module to handle nodejs connections rather than including them both in this package.

@benbrown
Copy link
Contributor

@nmaq-dev this branch has a working node implementation #119

@nmaq-dev
Copy link

Thanks for that 🙇

I'll poke at things. I started on the python side of things because I know it far better than js/ts/node. I can give it a shot and see if I can contribute any thoughts.

@Hunter275
Copy link
Member Author

@nmaq-dev The reason is that bundling the node dependencies causes issues when used in a browser unless you do extra build steps yourself which is a recipe for pain. I have some PRs open around this, but I think the likely path forward will be a separate module to handle nodejs connections rather than including them both in this package.

Exactly this.

@benbrown
Copy link
Contributor

benbrown commented Jan 2, 2025

@Hunter275 glad I got it right. I've got the working node class, I just need to bundle it up into a separate package.

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

Successfully merging this pull request may close these issues.

4 participants