Ilija
Ilija
Any plans on merging this in? It would be a major improvement over having to embed a 42Mb framework, that then sits in your repo unless you want to deal...
> @cspotcode Yes, as a short-term solution this can definitely be implemented using `bin` hooks to direct at the appropriate download location. I'll also try to take a look this...
cc @ibgreen
Having the same issue. `yarn --cwd foo/bar build` would exit with `Internal Error: ENOENT: no such file or directory, lstat '[REPO_DIR]/foo/bar/foo'`, unclear where the last `foo` is coming from
Same issue here using `@aws-sdk/client-secrets-manager`
Bisecting the version upgrades to understand where tracing stops working, it seems to be 1.3.9, everything seems well up until 1.3.8
@SaltyAom is this something that will be looked into? I understand there is a lot going on with the new major releases being rolled out, this seems like a blocker...
This is still happening, tried upgrading to 1.4.13 and the tracing is still broken, only 2 of the endpoints seem to be showing up in the Datadog dashboard for whatever...
@SaltyAom I've also tested with both jaeger and datadog and no traces are showing up for 1.4.x versions either. I'm struggling to find the time to provide a repro example...
Same error here on 1.3.5, not specifying either of the options just using the defaults