Chris Seckler
Chris Seckler
@lancedikson @voronianski Can we get this merged please? We rely heavily on your package in multiple places and would really love for our browser parsing to be the same in...
@connor-baer Thanks for the fix! I forked it and tested it and it looks like your solution needs to be applied on 4 more areas in the `parser.js` file where...
Vielen Dank!
I figured out that there is conflict with your package and this package: "laravel/cashier": "~2.0" How can I figure out what sort of conflict is causing the error to occur?
@pedronauck I'm experiencing the same issue as @yo7. Steps taken: 1. Clone repo 2. cd to `example` folder 3. `yarn install` 4. `yarn dev` 5. Click on `Alert` or `Button`...
@fatfisz I just noticed your comment and think I may be experiencing the same issue: > It's just a shame that Node.js' path resolution algorithm doesn't handle something like ~/path/to/project/file,...
Any examples on how to make this work with ES6 import syntax?
Yeah, i'm running into the same issue. Not even an empty string works.
@DanielRuf Can you provide an example on how to implement this yourself? I am pretty lost on where to even begin with that.