-
Notifications
You must be signed in to change notification settings - Fork 16
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
updated all packages to latest #15
Conversation
Hey friends - wanted to let you know, making this major upgrade in a minor release broke our build. It would be better if something like this were in a major version release, so that it didn't get silently pulled in via subdependencies. As in the latest version of Axios they also changed the import structure. For anyone else who happens to discover this today, what I've tried so far:
EDIT: I ended up forking the upstream package, hard resetting it to an old commit, updating the package.json to rely on axios-ntlm-1.3.0, and building and committing the compiled files. Then installing via the git repo instead of npm. In case anyone else needs a temporary solution as fast as possible. |
axios-ntlm uses axios docs latest It seems the same, what changed in axios import structure ? |
@vision10 I'm guessing it's this: https://github.com/axios/axios/releases/tag/v1.2.0
|
I am still using "axios": "~0.27.0", after update axios-ntlm to 1.3.1, it throws such error. Here is the full error log for your reference:
Since the error throws from Since axios-ntlm is somehow like a plugin of axios, having a sub-depdenency may not be a good idea. I would suggest that using peerDependencies to prevent the sub-depdenency issue. For more details, please read: |
would updating the package to version 1.4.0 solv the problem? |
@vision10 version 1.4.0 of what? you mean making another release of this package which reverts the change? |
same problem, also related to axios and soap, like #14 |
No description provided.