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
Try to launch 'yarn i18n:extract', node crash with error - never did ever, never could work (tried w/ yarn and node run)
node:internal/validators:119
throw new ERR_INVALID_ARG_TYPE(name, 'string', value);
^
TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
at new NodeError (node:internal/errors:371:5)
at validateString (node:internal/validators:119:11)
at Object.resolve (node:path:1098:7)
at o (/home/eric/devRoot/appcommunity/node_modules/@ngneat/transloco-keys-manager/utils/path.utils.js:1:1538)
at Array.map (<anonymous>)
at resolveConfigPaths (/home/eric/devRoot/appcommunity/node_modules/@ngneat/transloco-keys-manager/utils/path.utils.js:1:1581)
at resolveConfig (/home/eric/devRoot/appcommunity/node_modules/@ngneat/transloco-keys-manager/utils/resolve-config.js:1:1127)
at buildTranslationFiles (/home/eric/devRoot/appcommunity/node_modules/@ngneat/transloco-keys-manager/keys-builder/index.js:1:513)
at Object.<anonymous> (/home/eric/devRoot/appcommunity/node_modules/@ngneat/transloco-keys-manager/index.js:2:1008)
at Module._compile (node:internal/modules/cjs/loader:1095:14) {
code: 'ERR_INVALID_ARG_TYPE'
}
Expected behavior
Should extract keys ??
Please provide a link to a minimal reproduction of the bug
Is there an existing issue for this?
Is this a regression?
Yes
Current behavior
Try to launch 'yarn i18n:extract', node crash with error - never did ever, never could work (tried w/ yarn and node run)
Expected behavior
Should extract keys ??
Please provide a link to a minimal reproduction of the bug
n/a
Transloco Config
Debug Logs
No response
Please provide the environment you discovered this bug in
Additional context
Tried to DEBUG=* config seems coherent.
I would like to make a pull request for this bug
Yes solved here : #134
The text was updated successfully, but these errors were encountered: