Dennie de Lange

@19majkel94 : what is your issue with the monorepo?

A workaround is posted by swashata @ https://github.com/bmewburn/vscode-intelephense/issues/600#issuecomment-639525222 . Class aliasing is at the root of the problem. So at this moment I have a helper class: ```

I have exact the same issue: https://svelte.dev/repl/b1156db2f4304877848964581e4ac671?version=3.49.0 It does work with `$$props` instead of `$$restProps` and even with the options included in the select directly.

As a workaround, you can use: ``` isDragging: (monitor as any).internalMonitor.isDragging(), ```

So I believe it's because the clientWidth can't be calculated correctly. This can be fixed by adding `minWidth:0` on the `content` class of the `Layout` component.

I think react-admin, what I've debugged is that the tabs container needs a fixed width container. Setting `minWidth` accomplishes this.

You can use `lodash/debounce` function, something like (untested code): ``` import {Field} from "react-final-form"; import debounce from "lodash/debounce" class DebouncingValidatingField extends React.Component{ validate = debounce(this.props.validate,500) render(){ return } } ```

@pmoeller91 : I see you're right: you can try this: ``` import React from "react"; import PropTypes from "prop-types"; import { Field } from "react-final-form"; class DebouncingValidatingField extends React.Component {...

Something like: https://github.com/tkvw/warthog/tree/monorepo

> * Which pieces of Nest.js do you want that warthog doesn’t provide? * Maturity, nice separation of concerns, lots of tests, high involvement, good docs. For me there's no...