Invalid package.json field for sub packages

[BreakBB]

Description

The package.json in released sub packages such as is-debug reference a "bundle.js" in their main field which is only valid for the core module.

awesome-cordova-plugins/scripts/tasks/publish.ts

Line 18 in d7c771b

main: 'bundle.js',

That results in an issue for newly created vite projects:

import {IsDebug} from '@awesome-cordova-plugins/is-debug';

Error: Failed to resolve entry for package "@awesome-cordova-plugins/is-debug". The package may have incorrect main/module/exports specified in its package.json.

Proposal

The publish.ts should become aware of the modules it is building the package.json for and drop the main field for everything except the core module.

[Tallyb]

This is critical! it makes the packages unusable with variety of tools

[daohoangson]

Apparently this was introduced 2 years ago via #3483:

• generateLegacyBundles was added to rollup CJS from core/index.js and plugins/**/ngx/index.js.
• The core index file is in root so its bundle.js is put there
• The plugin's one is in ngx directory so the generated file is in the subdirectory
• The main field in PACKAGE_JSON_BASE doesn't take this into account so it always references the root file and triggers warning in different tools.

There are 2 approaches to fix for this IMHO:

1. Update generateLegacyBundles to target plugin root index.js file instead of the Angular one.
2. Or adjust main field for plugins

I think the first approach is more correct. Paging @laurentgoudet, what do you think?

[coltanium13]

We have noticed this same issue in our vite project, with the web-intent sub package as well. If you remove the main property from the web-intent's package.json file, it seems to work ok. Can we get a fix to these sub packages? Thank you!

[BreakBB]

Any news on this @danielsogl ?

[github-actions]

There has been no recent activity and this issue has been marked inactive.

[BreakBB]

The repo doesn't seem to be abandoned, still there is no reply from a maintainer?

[github-actions]

There has been no recent activity and this issue has been marked inactive.