Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update module import and export to remove DEP0148 depreciation warning #1047

Closed
bidoubiwa opened this issue Oct 11, 2021 · 5 comments
Closed

Comments

@bidoubiwa
Copy link
Contributor

bidoubiwa commented Oct 11, 2021

When building the repo in node version 16 the following warning occurs:

babelHelpers: 'bundled' option was used by default. It is recommended to configure this option explicitly, read more here: https://github.com/rollup/plugins/tree/master/packages/babel#babelhelpers
(node:37395) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at /Users/charlottevermandel/MeiliSearch/meilisearch-js/node_modules/rollup-plugin-typescript2/node_modules/tslib/package.json.
Update this package.json to use a subpath pattern like "./*".
(Use `node --trace-deprecation ...` to show where the warning was created)

The warning raises the Depreciation warning with the id DEP0148.

Sub-patterns should be used instead.

related #913

@Rishabhraghwendra18
Copy link

Hi @bidoubiwa . I am not able to find the folder package.json folder in which this issue is arising . I think it's arising in the tslib/package.json file . May you guide me in which file I have to make changes ?

@bidoubiwa
Copy link
Contributor Author

I think all files in /src are concerned.

You can reproduce the error by doing yarn build

@Rishabhraghwendra18
Copy link

ok... so I have to install node version 16 too

@Rishabhraghwendra18
Copy link

@bidoubiwa I have reproduced the warning but I am not able to figure out till now where I have to make the changes 😅 . I am new to this type of issue

@bidoubiwa
Copy link
Contributor Author

Hello @Rishabhraghwendra18, I looked at the problem and it seems to come from tslib like you said. We cannot directly change its package.json. We need to wait for them to update theirs. A pr is already open in their repository to fix the problem. I'm sorry this means there is indeed nothing to fix in this repo. I'm closing the issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants