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
We are installing multiple plugins into the Salesforce CLI which uses this plugin.
Currently, it seems that changing the order we install plugins in changes yarn's hoisting behaviour, which can cause incorrect module versions to be required in a plugin.
Expected behaviour
The order plugins are installed should not cause changes in execution behaviour.
Current behaviour
The order plugins are installed causes dependencies to be incorrectly required, potentially causing significantly different behaviour depending on installation order.
Screenshots
Failure case:
Success case:
Steps to reproduce
Success case Dockerfile:
FROM node:18
RUN npm install -g @salesforce/cli
RUN sf plugins install @salesforce/sfdx-scanner && \
sf plugins install @salesforce/plugin-packaging && \
sf plugins install @salesforce/plugin-community && \
echo y | sf plugins install sfdx-git-delta && \
sf plugins install sfdmu && \
sf plugins install @salesforce/plugin-signups
Failure case Dockerfile:
FROM node:18
RUN npm install -g @salesforce/cli
RUN sf plugins install @salesforce/sfdx-scanner && \
sf plugins install @salesforce/plugin-packaging && \
sf plugins install @salesforce/plugin-community && \
sf plugins install @salesforce/plugin-signups && \
sf plugins install sfdmu && \
echo y | sf plugins install sfdx-git-delta
Build the dockerfiles and run any command from the @salesforce/sfdx-scanner plugin.
Command used when debugging this was sfdx scanner:rule:add --language xml --path temp.xml.
Description
We are installing multiple plugins into the Salesforce CLI which uses this plugin.
Currently, it seems that changing the order we install plugins in changes yarn's hoisting behaviour, which can cause incorrect module versions to be required in a plugin.
Expected behaviour
The order plugins are installed should not cause changes in execution behaviour.
Current behaviour
The order plugins are installed causes dependencies to be incorrectly required, potentially causing significantly different behaviour depending on installation order.
Screenshots
Failure case:
Success case:
Steps to reproduce
Success case Dockerfile:
Failure case Dockerfile:
Build the dockerfiles and run any command from the @salesforce/sfdx-scanner plugin.
Command used when debugging this was
sfdx scanner:rule:add --language xml --path temp.xml
.sfdx version information:
The text was updated successfully, but these errors were encountered: