Closed kuznetsov-from-wonderland closed 3 years ago
I guess this issue will probably disappear if I upgrade to Node v14 ☝️
This is sad. I've had to forcibly transpile it with Babel, and I'm not sure if it's the reason I'm unable to have UI KItten properly tree-shaken 🤔
Node v14 solves this problem
Please add to documentation that Node v14 is now a requirement.
Upgrading to Node v14 does not work for me
🐛 Bug Report
To Reproduce
Steps to reproduce the behavior: jest.config.js
package.json
babel.config.js
tsconfig.json
ok.test.tsx
failed.test.tsx
Expected behavior
Link to runnable example or repository (highly encouraged)
UI Kitten and Eva version
And I also know that all UI-Kitten components should be rendered in a provider. I have a custom render fn just like this
this, by the way, does not work ether, because of the same transpilation error
The babel transpilation magic seems to work just fine according to first example. I have no idea of why this can be broken if I use any
@ui-kitten
componentYou are welcome!
Environment information