fix(module): correct ESM for Node usage #1214

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.

Sign up for GitHub

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

Draft

Haroenv wants to merge 3 commits into next from fix/extensions

+353 −0

Draft

fix(module): correct ESM for Node usage #1214

add package.json to exports

Codacy Production / Codacy Static Code Analysis required action Aug 13, 2024 in 0s

4 new security issues (0 max.).

Here is an overview of what got changed by this pull request:

Issues
======
- Added 4
           

Complexity increasing per file
==============================
- scripts/babel/extension-resolver.js  5

See the complete overview on Codacy

Annotations

Check warning on line 110 in scripts/babel/extension-resolver.js

codacy-production / Codacy Static Code Analysis

scripts/babel/extension-resolver.js#L110

Detected possible user input going into a `path.join` or `path.resolve` function.

Check warning on line 157 in scripts/babel/extension-resolver.js

codacy-production / Codacy Static Code Analysis

scripts/babel/extension-resolver.js#L157

Detected possible user input going into a `path.join` or `path.resolve` function.

Check warning on line 190 in scripts/babel/extension-resolver.js

codacy-production / Codacy Static Code Analysis

scripts/babel/extension-resolver.js#L190

Detected that function argument `{ types }` has entered the fs module.

Check warning on line 190 in scripts/babel/extension-resolver.js

codacy-production / Codacy Static Code Analysis

scripts/babel/extension-resolver.js#L190

The application dynamically constructs file or path information.

View more details on Codacy Production