Filip Nordling
Filip Nordling
@silentmatt - Glad you're on it! Just realized I couldn't access properties within an array :(
@pierpo The workaround is to do `numberValue.toString()` I guess? And to answer your question regarding if this works in `styled-components`. Yes, it does work.
This happens to me too. Since that one node process is never killed after build script, it blocks the dist folder from being rewritten on next build script. Apparently NX...
`pJSDom[0]` is the first pJS object that you can access and change its `particles` properties.
It appears that whenever a re-render runs because of the document prop constantly being a new reference, something breaks inside. So if you memoize the object that is being passed...
@paragraje Instead of passing a new object for the `document` prop on each render, create a memoized object: ```js const imageLink = Router().generate('app_document_getdocumentpage', { pageId: document?.pages[0]?.id }); const doc =...
@merlosy Yes but it seems like this plugin completely overrides/ignores that config.
I fixed this with a simple workaround inside the app itself (React app) by having a `beforeunload` listener on the window to unmount the app before the page actually reloads....
@jsonnull Yeah there is no leak actually happening. I was just saying there is a risk for it if devs aren't aware that no cleanup is being made to subscriptions...
Same problem here. In the meanwhile, you can add a ref to the direct parent of the `` component and then find the right node using different HTMLElement methods like...