-
Notifications
You must be signed in to change notification settings - Fork 39
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
get-object-path issues + proposal #157
Comments
Glad someone else is also experiencing this issue. I'm trying to deploy on Modulus and it is giving me an error about get-object-path as well because of Ampersand-View. Does anyone know a work around for this? |
I managed to get them installing by:
Not sure why trying to YMMV, @KayBeSee |
@dhritzkiv, if you want to stage a patched 8.x version, i'd be happy to publish it |
FTR, the current version (even at the time of issue filing) uses lodash.get |
Yep. However, non-official ampersand modules may be stuck on ampersand-view < v8.0, and won't install properly (as get-object-path fails) But I'm now rethinking the efficacy of creating and publishing a patched version of v8, as the majority of 3rd-party ampersand modules may be using versions older than 8: v7, v6, etc. A patch for v8 wouldn't address those versions. I don't believe there's a way to completely and gracefully recover from the npm module liberation situation. Best to just move on. |
@dhritzkiv, good point, i didn't consider that! |
Seems that some of my modules rely on
ampersand-view@v8.*
. However, this version ofampersand-view
relies onget-object-path@v0.0.2
(which was unpublished). Any chance for a "maintenance/patch" release (v8.0.2) ofampersand-view
that depends onget-object-path
that was republished as v0.0.3?Not sure if that'll fix install woes.
The text was updated successfully, but these errors were encountered: