-
Notifications
You must be signed in to change notification settings - Fork 25
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
incompatible version of amqpuri
#90
Comments
@puttpotsawee Thanks for letting me know of this. I apologize for the inconveniences. Could you please share a snippet showing how you are declaring/creating your AMQP connection URI (hide/change any sensible information on it)? Even if it is just a string on |
I mostly use I use this configs
thise configs will be push to and when in my
notice the payload data which is included in a single object along with
though, i have my own wrapper wrap the I hope this helps |
@puttpotsawee I believe I've found what the issue is here. You are running the plugin on node Shrinkwrapping (or yarn) might be your safest bet. My apologies for the inconvenience. |
@nfantone Thanks for your help! It really works on node |
@puttpotsawee You're welcome. It's on the |
Recently I had an absurd error on
seneca-amqp-transport
on the service that had been run on production for a while, the error says:Because I dockertized all my services and there're only newly build containers show this error, I assume it must be the incompatible version of dependencies, this is the dependencies on the working container:
and this is, for the not-working-version;
notice the version of
amqpuri
dependency,I think there should be the dependency lock or some kind??
right now, my fix was that I need to use npm shrinkwrap to create a dependency lock file
npm-shrinkwrap.json
in your project directory,after a clean
npm install
the amqp transport will continue to workThe text was updated successfully, but these errors were encountered: