Peter Mikitsh

I've confirmed that @hkjorgensen's recommended fix works. Thanks Henrik!

+1 for getting this PR'ed...

I came across this issue and can confirm adding the following babel config to each microfrontend resolved the issue: ```json { "plugins": [ [ "babel-plugin-styled-components", { "displayName": true } ]...

I ran into this issue with Yarn Classic (v1) and the workaround was to downgrade from npm v7 to npm v6: ``` npm i -g npm@6 ```

@deiucanta In the meantime, until this feature gets released, you could use longer-lived tokens. Once released, you can rotate your auth secret to a new value to wipe out all...

On the topic of refresh tokens: > Refresh tokens carry the information necessary to get a new access token. In other words, whenever an access token is required to access...

So the object passed in to the create API's [data argument](https://docs.feathersjs.com/api/services#createdata-params) will be mutated by the hooks?

Maybe I could write a global before create hook to augment the behavior: ```js function makeACopy(context) { context.data = Object.assign({}, ...context.data); return context; } app.hooks({ before: { create: [makeACopy] }...

I agree that it could be a fairly significant breaking change, but it'd be a worthwhile one to make. At least in the example I showed, it could be a...

After looking through other issues (ex: https://github.com/emotion-js/emotion/issues/2502#issuecomment-940106585), it seemed clear disabling speedy was the fix-- but I wasn't sure how to turn it off. It's an option you can provide...