-
Notifications
You must be signed in to change notification settings - Fork 86
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 install can break server-side path to client-side dependency /assets/superagent.js #185
Comments
@joelpurra: Can you try this branch please? https://github.com/XhmikosR/slackin-extended/tree/fix-superagent |
@XhmikosR: due to the locked-down nature of the particular system where the issue was discovered, I can't test your branch in the exact same way as before. Tested (without the production slack configuration) on a dev machine (with the same/similar Versionsnode --version
npm --version
Pathsnpm ls superagent
ls -l -d ./node_modules/{slackin-extended,superagent}
|
Cool, it was easier to fix than I thought then 🙂 PR: #187 |
Thank you :) Let me test the PR and merge. |
The client-side dependency
/assets/superagent.js
is given special server-side path treatment inindex.js
.On my system
/assets/superagent.js
returns HTTP error 404 and breaksslackin-extended
client-side. This is due to (changes in) hownpm install
places dependencies, which may be optimized between packages in the samepackage.json
.Versions
Am running slightly older versions due to
apt
on Debian 10 Buster.Paths
Perhaps something like
resolve-pkg
could be used in the short-term, but replacingsuperagent
with something else might be a better long-term solution. See also #86.Originally posted by @joelpurra in #86 (comment)
The text was updated successfully, but these errors were encountered: