Tarik Lafi
Tarik Lafi
in my case i am using rollup to bundle nodejs project, i'm using vscode, the solution of changing the version like: ``` "babel-plugin-module-resolver": "^2.7.1", or v2 "eslint-import-resolver-babel-module": "2.2.1", or v2...
After trying lots of non detailed solutions that didn't worked well for me, i made it working using all last versions: - `"@babel/core": "^7.0.0-beta.46",` - `"eslint": "^4.19.1",` - `"eslint-plugin-import": "^2.11.0",`...
that was quite confusing.
glad that the config worked for all of you! @jefrydco i just combined some configs from many places, that was kind of mysterious.
also i tried to use it with **svg** to keep a good quality but i couldn't **resize** it, any explanation ? thanks.
Thanks, I've handled it with global style, it's not worth it to compile it locally, I've opened this issue because the docs describes the padding prop and it could be...
Hello and thanks for the solution proposed! I don't understand why this is not implemented inside the library yet ? It was not too simple to test the up-voted solution...
Agree, very odd .. i think this packages is helping with `swiper` custom builds, Swiper alone has some issues for example using it along with nextjs the dev build or...
Hi and thanks for reporting,I've got an other similar issue! it's hard to find useful information about this issue since the typescript config `KeycloakConfig` is missing the realm-public-key prop already...
Migrations with typerom still a big mess !