Daniel Tschinder
Daniel Tschinder
I have mixed feelings about this. I do not like the code duplication from the server-side. In case we ever decide to change the logic server-side this can create problems...
I personally feel this is okay if we add a message like `leave empty for autogenerated name`. Ping @netlify/developer-experience-members What is your take on this? Any recommendations?
I'm not working till end of September. So i can look then or someone else does. Sorry
@tinfoil-knight I rebased on the current main branch and fixed the tests. It seems the tests match on the exact input line.
Needs code changes.
This might be an issue with npm. (see https://stackoverflow.com/questions/69567381/getting-cannot-read-property-pickalgorithm-of-null-error-in-react-native) Can you try the suggestions there?
Thanks for reporting.
I think we cannot solve this right now, because there are some dependencies that we cannot yet update because of either ESM compatibility or node version restrictions.
Are you using node 18? If so try to use node 16 for now, this should fix it. We are working on this, see #4845.
These issues should be fixed now as of version 12.0.2. If it still appears please reopen with an example.