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
Starting from the latest node version (22.12) the use of importAssertions is deprecated.
You already have related to this deprecation in hook.js, but since you still use it, node still outputs a warning for using it.
The relevant code:
// Node.js v21 renames importAssertions to importAttributes
if (
(context.importAssertions && context.importAssertions.type === 'json') ||
(context.importAttributes && context.importAttributes.type === 'json')
) {
return result
}
The warning that node outputs:
(node:22772) ExperimentalWarning: Use `importAttributes` instead of `importAssertions`
(Use `node --trace-warnings ...` to show where the warning was created)
The implications of it are that the warning seems intimidating and it is uncontrollably verbose, only because I used import-in-the-middle as a third party package. I would love for a follow up 😄
The text was updated successfully, but these errors were encountered:
Starting from the latest node version (22.12) the use of
importAssertions
is deprecated.You already have related to this deprecation in hook.js, but since you still use it, node still outputs a warning for using it.
The relevant code:
The warning that node outputs:
The implications of it are that the warning seems intimidating and it is uncontrollably verbose, only because I used import-in-the-middle as a third party package. I would love for a follow up 😄
The text was updated successfully, but these errors were encountered: