-
Notifications
You must be signed in to change notification settings - Fork 5
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
NPM module cannot be imported #2
Comments
Hey scranen, thank you for this detailed issues description. I certainly need to work on the published version. I had to publish a version 1.0.0 quite early because I was given the name 'opcua' on npm. Someone else had the name but didn't use it and didn't have any code behind it. However after they've given me the name I had to release a new major version that includes at least some code from my repo. So that's about the history of this project on npm. The published version is certainly out of date. However I'm not yet ready to release a next version. If you want to play with I'm curious, what are you using as the server? Best regards, |
Thanks for the pointers, I'll have a look. The server I'm talking to is probably an old version of the one that's integrated in Codesys (didn't really look into it, I'm doing a quick and dirty PoC on a badly documented device), using my own solution to convert it to websocket. |
Hello, Do you have a solution for me? Thank you and have a nice day. |
Hi,
|
Out of the box, loading the module does not seem to work for me.
Steps to reproduce
Expected result
The import statement should succeed.
Actual result
Further information
The text was updated successfully, but these errors were encountered: