Colum Ferry
Colum Ferry
I'm gonna chime in. I don't think the right solution is to change Transloco and stop it from using `providedIn` which is the defacto option from Angular as it supports...
I'm not quite sure you fully understand `providedIn: 'root'`, or perhaps I'm not understanding you correctly. `providedIn: 'root'` will only set the Provider at the root level of the Injection...
What are i18n and l10n requirements for the friendly message?
I can't reproduce this on `macOS`, so it seems limited to a windows issue.
For anyone coming to this issue that is encountering the same problem with their local workspace plugins, the workaround is to point your executor to your local plugin: ```json "targets":...
Hi @statop ! Can you provide an example even just as a comment here of when this occurs and why this is a bug? We only need to move projects...
This should be solved by this line, no? https://github.com/nrwl/nx/blob/81be1e5419f784b502ced35965b215e10b50d377/packages/react/src/executors/module-federation-dev-server/module-federation-dev-server.impl.ts#L76 I know now how to test this at least
@statop I cannot reproduce that behaviour on the latest version of Nx. If you can provide a reproduction repo, I'll happily reopen this and take a look.
Hi @statop ! You can fix this easily by adding the following to the `"targetDefaults"` object in `nx.json`. For Angular: ```json "@nx/angular:webpack-browser": { "inputs": [{ "env": "NX_MF_DEV_SERVER_STATIC_REMOTES" }] }, ```...
@statop this would mean you need an express instance for every static remote though right?