Closed simondotm closed 1 year ago
e2e tests failing for some reason I'm trying to figure out. Not working on my local either anymore.... Nx not picking up the imported buildable library dependency - latest version of Nx should detect this and auto-build it before trying to build the functions app.
Ok so building before and after updating a source file changes the error (no deps detected), but 2nd build just used cached output from 1st build. So changes to source files in the e2e test in between are not being detected by Nx for some reason. Classic Nx experience.
Fed up with this now, spent too much time on it. The e2e test workspace simply does not calculate dependencies properly. I'm getting various different errors:
package.json
@nrwl/js
plugin config to force analyzeSourceFiles
to true makes no difference (which is shouldnt anyway)@nrwl/js:tsc
executor doesnt like being used to build apps (it only has lib generator now)? @nrwl/node:node
executor is no use, nor is the @nrwl/node:webpack
executor, as we just want to typescript compile our functions code. (which @nrwl/node:package
used to do, but this has been removed from Nx)My overall hunch is that these issues are all e2e workspace related, so lets see if the plugin works when installed in a real workspace.
Oh and updating to v15.3.0 of Nx seems to mean that all generated tsconfig
files have changed which doesn't give confidence that Nx is anywhere close to stable.
I like Nx, but boy my experience is that it is persistently buggy and the amount of things that change between releases is wild.
Despite multiple attempts by contributors and myself, it was very difficult to cleanly retrofit the plugin to newer versions of Nx. So the whole plugin has been rewritten from scratch:
@nrwl/js:tsc
plugin as a base--watch
in the plugine2e patch
shenanigansThis first step enables next steps & aims which are to support:
codebase
feature--watch
onserve
commands