Error invoking SVGAnalyzer about pal HOT 11 CLOSED

Is this coming from inside a test? It looks like you haven't initialize the PAL in the testing environment. Can you provide some more info?

from pal.

No they are real Aurelia components living in a separate repo. We have the repo npm linked to our Aurelia app. I need to get the components to use the same instance of Aurelia as our app.

from pal.

I'm having a hard time understanding what the setup is. How are you "running" the components outside of the app? On a related note, please update your Aurelia libs to make sure it's not something we fixed. We had a bunch of releases today.

from pal.

Thank you for your patience,
I mocked up a simplified version of the issue using aurelia-skeleton
https://github.com/itsnatscott/binding-issue.

from pal.

I guess from your lack of response that I am pretty off target here?

from pal.

I was on vacation.

from pal.

@jdanyow Can you look into this?

from pal.

@itsnatscott does the issue reproduce when you manually copy the components into your app's node modules folder (instead of npm link)?

from pal.

@EisenbergEffect @jdanyow Thanks for looking into this!
If I copy directly into node modules the SVGAnalyzer error doesn't occur, but the component does not get the bound data either.

from pal.

This just popped up for me. It only occurs when testing local changes to aurelia-binding referenced with npm link. I am open to workarounds if you guys have a different way to test local framework changes besides npm link.

from pal.

Why is this closed? The issue still exists as @jonathaneckman described it using npm link.

from pal.