Closed jkerr5 closed 6 years ago
I can get things to run again by setting an explicit dependency on featureserver 2.11.1.
Patch on the way. Sorry, it got npm published without a compile.
Just published a patch (v2.12.1). This time, compiled, with the result dist
directory. You can upgrade with yarn upgrade
.
Thanks. I'll give it a try.
On Thu, May 3, 2018 at 9:52 PM Rich Gwozdz notifications@github.com wrote:
Just published a patch (v2.12.1). This time, compiled, with the result dist directory. You can upgrade with yarn upgrade.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/koopjs/FeatureServer/issues/105#issuecomment-386487220, or mute the thread https://github.com/notifications/unsubscribe-auth/AAP8AmFFbkCtJK0wtd2NwGxhkSl5AABBks5tu7RhgaJpZM4Tx_SN .
Looks good
When I install from scratch and try to run a koop provider, I now get the following stack trace
This happens for both the MarkLogic provider I am working on as well as the koop-sample-app. The
featureserver
directory is there but there is nodist
folder after runningnpm install
.