You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the effects of this bug are that fastboot cannot be used in conjunction with more recent versions of yarn, pnpm, or pnp strategies that avoid hoisting dependencies to root.
This affects resolution of whitelisted dependencies both from the project and from addons it consumes.
For instance, ember-fetch declares both a dependency and whitelistes abortcontroller-polyfill. Even if the consuming app also adds abortcontroller-polyfill to its dependencies and adds the same whitelisted values, when hoisting does not occur this will fail to be resolved by the sandboxedRequire provided by fastboot-schema.js which scopes to a directory that will not be able to see it and executes from a directory that does not have the parent project in its path.
Example failure of this in which the parent project has re-declared the dependency and re-declared the whitelisted values:
the effects of this bug are that fastboot cannot be used in conjunction with more recent versions of yarn, pnpm, or pnp strategies that avoid hoisting dependencies to root.
This affects resolution of whitelisted dependencies both from the project and from addons it consumes.
For instance, ember-fetch declares both a
dependency
and whitelistesabortcontroller-polyfill
. Even if the consuming app also addsabortcontroller-polyfill
to its dependencies and adds the same whitelisted values, when hoisting does not occur this will fail to be resolved by the sandboxedRequire provided by fastboot-schema.js which scopes to a directory that will not be able to see it and executes from a directory that does not have the parent project in its path.Example failure of this in which the parent project has re-declared the dependency and re-declared the whitelisted values:
The text was updated successfully, but these errors were encountered: