Closed kspeakman closed 1 year ago
@MangelMaxime Is it possible to isolate the Nacara deps from the Test project deps? Was thinking it might be possible to have it in a separate folder with its own package.json. I'm not practiced in advanced front-end build scenarios.
Sorry, I didn't see that you took into account some of my comments and so was still waiting for after you... (my bad)
I will have a look at the dependencies stuff.
In theory, React 18 is compatible with React 17 with some warning.
No worries!
Ah, yes. I seem to be using React 18 with the older Fable.React package and see a warning on every render. I think this works because Fable.React is dotnet and can't enforce npm package deps. Could Nacara's npm deps be changed to allow both v17 and v18?
Supporting both react 17 and 18 is not that easy, because some import needs to be different.
I am just going to support React 18 for now. Nacara is under a complete rewrite right now, to delegate most a lost of responsibility to an external tool so I can focus on what make add values to Nacara (providing a good template for documentation + F# API generation in the future)
resolves #40
TODO