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
In Node 16 and up, running prettier-standard generates the following error:
(node:416235) [DEP0128] DeprecationWarning: Invalid 'main' field in '/home/saejin/projects/personal/indexify/node_modules/find-parent-dir/package.json' of 'find-parent-dir.js'. Please either fix that or report it to the module author
This is caused by a dependency of prettierx -- find-parent-dir. A fix was released as version 0.3.1 of that package, and incorporated in prettierx in version 0.18.2. The version of prettierx used in prettier-standard should probably be updated to 0.18.2 or 0.19.0 (the latest as of this issue); some preliminary testing by forcing resolution seems to not cause any issues.
In the meantime, people who encounter this issue can add the following snippet to their package.json, and Yarn will force prettierx version 0.19.0 (with patches) to be installed instead of the current 0.11.3. Npm has an old plugin to do the same, and a new RFC for the same functionality under a different name.
"resolutions": {
"prettierx": "~0.19.0"
}
The text was updated successfully, but these errors were encountered:
In Node 16 and up, running
prettier-standard
generates the following error:This is caused by a dependency of
prettierx
--find-parent-dir
. A fix was released as version0.3.1
of that package, and incorporated inprettierx
in version0.18.2
. The version ofprettierx
used inprettier-standard
should probably be updated to0.18.2
or0.19.0
(the latest as of this issue); some preliminary testing by forcing resolution seems to not cause any issues.In the meantime, people who encounter this issue can add the following snippet to their
package.json
, and Yarn will forceprettierx
version0.19.0
(with patches) to be installed instead of the current0.11.3
. Npm has an old plugin to do the same, and a new RFC for the same functionality under a different name.The text was updated successfully, but these errors were encountered: