-
Notifications
You must be signed in to change notification settings - Fork 19
Cannot read property 'x' of null #36
Comments
The SVG looks good to me. I dumped it into a test sprite and it built beautifully. How does your options look? |
Ahh I see strange... Sorry I should have included my options as well. Here are my options:
I just tested some things and it seems that I can build the SVG sprite all by itself but when I try to add sprites to it, it will fail? Here is another SVG I added to the folder. Not sure if it has something to do with specific SVG files or maybe it is my options?
And not sure if it helps but Appreciate all the help! |
I'm still not able to recreate the error :( So I'm just grasping at straws here - but:
|
Okay interesting I made a completely different folder with a fresh npm install of Then I tried setting it to And to answer your previous questions I'm running OSX 10.10.1 and I'm running EDIT: I just tried using it in my actual project and yeah it works fine if I set it to |
I don't think the bigger size would be an issue - besides if it's not the size you want ;) You might be on to something about using the |
Oh hmmm that's possible. Just checked and it seems I am indeed on 2.0.0. From the package.json
However, if you can't recreate the issue, I'm skeptical if this is actually a problem and maybe I just did something wrong? I'll investigate more and look into the |
Closing this for now until I can properly recreate the problem consistently. |
For some strange reason I am getting this error
Cannot read property 'x' of null
when making a sprite for this SVG. However, all my other SVGs that were also made the same way work fine...Here's a jsFiddle. I changed the fill color in the jsFiddle just to make it clearer what it is but originally I wanted it
#FFFFFF
. It's just a play button made by my friend.Is anyone able to reproduce the error with this SVG code? I will try to look into the cause of it and report back if I find anything but until then if anyone has advice I would appreciate it.
The text was updated successfully, but these errors were encountered: