Reviewing files that changed from the base of the PR and between 25c156d and bbfc1c9.

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

• components/algolia/package.json (1 hunks)
• components/amazon_ses/package.json (1 hunks)
• components/bandwidth/package.json (1 hunks)
• components/basecamp/package.json (1 hunks)
• components/blogger/package.json (1 hunks)
• components/brex/package.json (1 hunks)
• components/brex_staging/package.json (1 hunks)
• components/chartmogul/package.json (1 hunks)
• components/chatbot/package.json (1 hunks)
• components/commercehq/package.json (1 hunks)
• components/crove_app/package.json (1 hunks)
• components/customer_io/package.json (1 hunks)
• components/data_stores/package.json (1 hunks)
• components/demio/package.json (1 hunks)
• components/dev_to/package.json (1 hunks)
• components/discord_bot/package.json (1 hunks)
• components/doppler_ops/package.json (1 hunks)
• components/ecwid/package.json (1 hunks)
• components/emailoctopus/package.json (1 hunks)
• components/eventbrite/package.json (1 hunks)
• components/eversign/package.json (1 hunks)
• components/givebutter/package.json (1 hunks)
• components/http/package.json (1 hunks)
• components/inksprout/package.json (1 hunks)
• components/knack/package.json (1 hunks)
• components/mailchimp/package.json (1 hunks)
• components/microsoft_onedrive/package.json (1 hunks)
• components/miestro/package.json (1 hunks)
• components/mixmax/package.json (1 hunks)
• components/netlify/package.json (1 hunks)
• components/new_relic/package.json (1 hunks)
• components/orbit/package.json (1 hunks)
• components/papyrs/package.json (1 hunks)
• components/pointagram/package.json (1 hunks)
• components/quipu/package.json (1 hunks)
• components/raindrop/package.json (1 hunks)
• components/rd_station_crm/package.json (1 hunks)
• components/refersion/package.json (1 hunks)
• components/repairshopr/package.json (1 hunks)
• components/roll/package.json (1 hunks)
• components/sendgrid/package.json (1 hunks)
• components/sendoso/package.json (1 hunks)
• components/sentry/package.json (1 hunks)
• components/seventodos/package.json (1 hunks)
• components/shopify_partner/package.json (1 hunks)
• components/shortcut/package.json (1 hunks)
• components/siteleaf/package.json (1 hunks)
• components/smtp2go/package.json (1 hunks)
• components/spondyr/package.json (1 hunks)
• components/spotify/package.json (1 hunks)
• components/squarespace/package.json (1 hunks)
• components/ssh/package.json (1 hunks)
• components/stack_exchange/package.json (1 hunks)
• components/stormboard/package.json (1 hunks)
• components/strava/package.json (1 hunks)
• components/superdocu/package.json (1 hunks)
• components/teamgate/package.json (1 hunks)
• components/toggl/package.json (1 hunks)
• components/vend/package.json (1 hunks)
• components/voice_monkey/package.json (1 hunks)
• components/weworkbook/package.json (1 hunks)
• components/woxo/package.json (1 hunks)
• components/yotpo/package.json (1 hunks)
• components/you_need_a_budget/package.json (1 hunks)
• components/zerotier/package.json (1 hunks)
• components/zonka_feedback/package.json (1 hunks)
• components/zoom_admin/package.json (1 hunks)

• GitHub Check: pnpm publish
• GitHub Check: Verify TypeScript components
• GitHub Check: Publish TypeScript components

components/blogger/package.json (2)

3-3: Version Update Alignment

The version update from the previous version to "0.0.5" is clear and consistent with the module modernization efforts. Ensure that this version bump is also reflected in your release notes and package registry.

---

5-5: ES Module Entry Point Migration

Updating the "main" field from "blogger.app.js" to "blogger.app.mjs" correctly reflects the transition to ECMAScript modules. Please confirm that all import paths and build configurations within your component ecosystem are updated accordingly.

components/knack/package.json (2)

3-3: Version Bump Confirmation
The version update from "0.0.4" to "0.0.5" is correct and consistent with the overall module upgrades seen in this PR. Please ensure that any additional version references (e.g., changelogs) are also updated accordingly.

---

5-5: Main Field Update to ES Module
Changing the "main" entry from "knack.app.js" to "knack.app.mjs" properly signals a shift to ECMAScript modules, which should resolve import issues. Confirm that the referenced file uses valid ES module syntax.

components/sendoso/package.json (1)

5-5: Main Entry Point Update to ES Modules:
The main field now points to "sendoso.app.mjs", switching the module format to ES Modules. Confirm that all consumers of this package (such as build scripts or other integrations) are compatible with ES Modules and that documentation is updated accordingly.

components/data_stores/package.json (2)

3-3: Version Update Confirmation.
The version number has been correctly bumped from "0.1.8" to "0.1.9", aligning with the new release process.

---

5-5: Main Field Migration to ES Modules.
The update of the main field from "data_stores.app.js" to "data_stores.app.mjs" correctly reflects the transition to ECMAScript modules, addressing the import issue described in the PR objectives.

components/rd_station_crm/package.json (2)

3-3: Version Bump Updated
The version has been updated to "0.0.5" as part of this release. Ensure that this bump aligns with your semver guidelines and the intended changes in this PR.

---

5-5: Main Entry Point Updated for ESM Compatibility
The main entry point now references "rd_station_crm.app.mjs", correctly reflecting the migration to ECMAScript modules. Please verify that the referenced file exists and that the module exports are correctly defined.

components/shopify_partner/package.json (2)

3-3: Version Bump Update

The version has been updated from an earlier value (presumably "0.1.3") to "0.1.4". This minor increment is appropriate for the changes made and aligns with semantic versioning practices.

---

5-5: Main Entry Point Modification

The main file is now set to "shopify_partner.app.mjs", reflecting the transition to ECMAScript modules. This change aligns with similar updates across other components. Ensure that any consumers of this package update their import paths accordingly.

components/netlify/package.json (2)

3-3: Version Bump Confirmation

The version has been updated to "0.4.1", which is in line with the overall versioning progression for this package. This minor version bump correctly signals backward-compatible changes.

---

5-5: Main Entry Point Update Verification

The main entry point has been updated from "netlify.app.js" to "netlify.app.mjs", reflecting the transition from CommonJS to ECMAScript modules. This change should resolve the import issues described in the PR objectives.

components/voice_monkey/package.json (2)

3-3: Version Update: "version" field bump is correct.
The version has been updated from "0.0.3" to "0.0.4" to reflect a new release. Ensure that this change is in line with semantic versioning practices and that any dependent components are updated accordingly.

---

5-5: Main Entry Point Transitioned to ESM.
The "main" field now points to "voice_monkey.app.mjs", indicating a switch to ECMAScript modules. Please verify that the corresponding file exists and that related configurations elsewhere in the project are consistent with this change.

components/shortcut/package.json (2)

3-3: Version Bump Confirmed
The version has been incremented to "0.3.6" to reflect the update. This aligns with the broader transition outlined in the PR.

---

5-5: Main Entry Point Update Verified
Switching the main entry from "shortcut.app.js" to "shortcut.app.mjs" correctly aligns the package with ECMAScript modules. Please confirm that the file shortcut.app.mjs exists and is correctly implemented in the package directory.

components/roll/package.json (2)

3-3: Version Bump Update Confirmed.
The version has been correctly updated from the previous release (presumably "0.0.3") to "0.0.4", which aligns with semantic versioning practices for a minor release.

---

5-5: Main Entry Point Updated to ECMAScript Modules.
The main field now points to "roll.app.mjs", reflecting the transition from CommonJS to ECMAScript modules. This update should resolve the import issues described in the PR objectives.

components/sentry/package.json (2)

3-3: Version Update Verification
The version number has been correctly updated to "0.4.3", aligning with a new release. Confirm that all related changelogs and dependency management tools reflect this semantic update.

---

5-5: Main Entry Point Transition
Changing the main entry from "sentry.app.js" to "sentry.app.mjs" appropriately reflects the migration to ECMAScript modules. Ensure that all consumers of this package update their import paths accordingly.

components/woxo/package.json (2)

3-3: Version Update Verified.
The version bump from "0.0.4" to "0.0.5" correctly reflects the new release, ensuring semantic versioning aligns with the changes.

---

5-5: Main Entry Point Transition to ECMAScript Modules.
Updating the main field from "woxo.app.js" to "woxo.app.mjs" properly aligns with the project's shift toward ES Modules, which should resolve the import issues previously encountered. Ensure that the corresponding .mjs file exists and is correctly referenced in related documentation.

components/doppler_ops/package.json (2)

3-3: Version Bump Verification
The version has been correctly updated from "0.0.3" to "0.0.4". Ensure that this bump follows your project's semantic versioning conventions and that any consumers of your package are aware of this update.

---

5-5: Main Entry Point Update
The main entry point change from "doppler_ops.app.js" to "doppler_ops.app.mjs" is appropriate given the move toward ECMAScript modules. Please verify that all downstream references or import paths to this module have been updated accordingly.

components/weworkbook/package.json (2)

3-3: Version update validated.

The bump from "0.0.4" to "0.0.5" is appropriate for the new release. Ensure consistency if similar changes are made across multiple components.

---

5-5: Main entry point update to ES Modules.

Transitioning from "weworkbook.app.js" to "weworkbook.app.mjs" correctly reflects the switch to ECMAScript modules. Verify that the overall build and import mechanisms are compatible with this change.

components/zerotier/package.json (2)

3-3: Version bump is correctly applied.
The version update from "0.0.7" to "0.0.8" follows expected semantic versioning practices for a minor update related to import path fixes.

---

5-5: Main entry point update is effective.
Changing the main entry from "zerotier.app.js" to "zerotier.app.mjs" correctly transitions the package to using ECMAScript modules, addressing the import issues described in the PR objectives.

components/mailchimp/package.json (2)

3-3: Version Bump Correctness
The updated version from "1.0.3" to "1.0.4" is an appropriate increment that reflects the changes made. Make sure that any dependent systems are updated accordingly if they rely on strict versioning.

---

5-5: Main Entry Point Update
Updating the entry point from "mailchimp.app.js" to "mailchimp.app.mjs" correctly aligns with the transition to ECMAScript modules. This change should resolve the import issues previously observed.

components/chatbot/package.json (2)

3-3: Version Bump Confirmation

The version update to "0.0.5" is appropriate given the changes. Please make sure that this version bump is consistently applied across related components if necessary.

---

5-5: Main Entry Point Update to ES Modules

The main entry point has been updated from "chatbot.app.js" to "chatbot.app.mjs", which clearly indicates the shift from CommonJS to ES Modules. Ensure that the build and runtime environments are compatible with this change.

components/papyrs/package.json (2)

3-3: Version Update is Correct.
The version has been incremented from "0.0.2" to "0.0.3", which is appropriate given the changes to the main entry point. This minor update aligns well with semantic versioning practices.

---

5-5: Main Entry Correction to ECMAScript Module.
Changing the main entry point from "papyrs.app.js" to "papyrs.app.mjs" correctly reflects the transition to ECMAScript modules. Please ensure that the corresponding file exists and that any related documentation or build configurations are updated accordingly.

components/brex_staging/package.json (2)

3-3: Updated Version Number
The version was bumped from "0.0.4" to "0.0.5", which is consistent with proper semantic versioning. Ensure that all related documentation and changelogs are updated accordingly.

---

5-5: Updated Main Entry Point to ECMAScript Module
The main entry point has been updated from "brex_staging.app.js" to "brex_staging.app.mjs", aligning with the migration to ECMAScript modules. Please verify that the brex_staging.app.mjs file exists at the specified location and that all import statements across the codebase refer to the correct module file.

components/ssh/package.json (2)

3-3: Version bump update.
The version has been correctly incremented from "0.0.3" to "0.0.4". Please verify that this version bump aligns with the project's semantic versioning policy and that any dependent documentation (such as CHANGELOG or release notes) is updated accordingly.

---

5-5: Update to ES Module entry point.
Changing the main entry point from "ssh.app.js" to "ssh.app.mjs" reflects the transition to ES Module syntax as intended. Ensure that the file ssh.app.mjs exists in the expected location and that any import paths in the codebase have been updated to accommodate this change.

components/mixmax/package.json (1)

5-5: Main Entry Point Update is Valid.
Changing the main entry point from "mixmax.app.js" to "mixmax.app.mjs" correctly reflects the migration to ECMAScript modules, addressing the import issues outlined in the PR objectives.

components/siteleaf/package.json (2)

3-3: Version Number Update Confirmed.
The version has been updated to "0.0.4", which is consistent with the patch update strategy. Ensure that any downstream dependencies or consumers are informed about this increment.

---

5-5: Main Entry Point Transition to ECMAScript Module.
Changing the main entry point from "siteleaf.app.js" to "siteleaf.app.mjs" correctly reflects the shift to ECMAScript modules. This update should resolve import issues previously caused by an invalid file path. Verify that the corresponding app file exists at the specified location and that consumers of this package are configured to use ESM.

components/stack_exchange/package.json (2)

3-3: Version Bump Update is Appropriate.
The version number has been correctly bumped from "0.3.6" to "0.3.7". Please ensure that this change follows the semantic versioning guidelines established for the project.

---

5-5: Main Entry Point Transition to ECMAScript Modules.
The main entry now points to "stack_exchange.app.mjs", which reflects the shift to ECMAScript module syntax. Please verify that the "stack_exchange.app.mjs" file exists and contains the proper ESM syntax (e.g., using import/export). Also, ensure that any consumer code has been updated to correctly import an ESM module if needed.

components/vend/package.json (2)

3-3: Version Bump Verification
The version update to "0.0.4" correctly reflects the changes made in this PR. Make sure that the changelog and any dependency references in the repository are updated accordingly.

---

5-5: Main Entry Point Update
Updating the main entry point from "vend.app.js" to "vend.app.mjs" aligns with the migration to ECMAScript modules and fixes the import issue. Please verify that the file vend.app.mjs exists in the repository and is properly configured to be used as the module entry point.

components/spotify/package.json (2)

3-3: Version Bump Consistency

The version number has been updated to "0.7.2", which is consistent with the changes made. Ensure that corresponding changelogs and documentation are updated to reflect this version change.

---

5-5: Main Entry Point Update to ECMAScript Module

Changing the main entry point from "spotify.app.js" to "spotify.app.mjs" correctly marks the file as an ECMAScript module. This update should resolve the import issues outlined in the PR objectives.

components/quipu/package.json (2)

3-3: Version Update Verified

The version update to "0.0.3" is properly aligned with the PR objectives and indicates the intended new release iteration for the package.

---

5-5: Main Entry Point Update Confirmed

Changing the main entry from "quipu.app.js" to "quipu.app.mjs" correctly reflects the switch to ECMAScript modules, as outlined in the PR description. This change will ensure that the package can be imported correctly in Node.js code steps.

components/dev_to/package.json (2)

3-3: Version Bump Approved.
The version update from "0.3.9" to "0.3.10" is correctly applied and aligns with the release requirements.

---

5-5: Main Entry Point Format Change.
Updating the "main" field from "dev_to.app.js" to "dev_to.app.mjs" reflects the transition to ECMAScript modules and should resolve the import issues experienced earlier.

components/commercehq/package.json (2)

3-3: Version Bump Confirmation
The version update to "0.0.4" is clear and adheres to semver practices for a patch release. Ensure that all related documentation and changelogs reflect this update.

---

5-5: Main Entry Point Update
Switching the main entry file from "commercehq.app.js" to "commercehq.app.mjs" correctly signals the migration to ECMAScript Modules. Please verify that the file commercehq.app.mjs exists and is correctly configured to export the necessary functionality.

components/eventbrite/package.json (2)

3-3: Version Bump Verification

The version number update to "0.1.1" is appropriate given the changes. This minor bump accurately reflects the incremental update without implying breaking changes.

---

5-5: Main Entry Point Update

Updating the main file from "eventbrite.app.js" to "eventbrite.app.mjs" correctly reflects the transition to ECMAScript modules and should resolve the import issues described.

components/eversign/package.json (2)

3-3: Version Bump is Correct.
The version update to "0.0.3" is consistent with other component changes and signals the proper update to align with the new main entry point.

---

5-5: Updated Main Entry to Reflect ESM Transition.
Changing the main entry from "eversign.app.js" to "eversign.app.mjs" is in line with the project-wide shift to ECMAScript modules. Ensure that the corresponding file eversign.app.mjs exists and is properly configured in the repository to avoid runtime import issues.

components/yotpo/package.json (1)

3-3: Version Bump Confirmation

The version has been correctly updated to "0.3.6", which is consistent with the changes made for this release.

components/chartmogul/package.json (2)

3-3: Version Bump is Correct.
The update of the version from the previous release to "0.0.4" aligns with the expected component update strategy. Please ensure that this version number is in sync with related components if needed.

---

5-5: Updated Main Entry Point.
The change from "chartmogul.app.js" to "chartmogul.app.mjs" correctly reflects the intended migration to ES modules, ensuring that the package can be imported correctly. Confirm that the corresponding file (chartmogul.app.mjs) exists and is correctly configured.

components/new_relic/package.json (1)

3-3: Version Update Confirmed.
The version has been correctly updated from a previous version to "0.0.5" in line 3, which aligns with the intended release process.

components/discord_bot/package.json (2)

3-3: Version Bump Update Confirmed.
The version has been updated from "0.6.0" to "0.6.1", which is consistent with a minor release change. Ensure that any dependent consumers are aware of this update.

---

5-5: Correct Main Entry Update.
The main entry point has now been updated to "discord_bot.app.mjs", which correctly reflects the transition to ECMAScript modules. Please verify that the specified file exists and is properly configured as an ESM module.

components/inksprout/package.json (2)

3-3: Version Bump Verification
The version update to "0.0.5" is clear and aligns with the expected incremental release. Ensure that all related documentation and dependent components reflect this version, if applicable.

---

5-5: ECMAScript Module Transition
Updating the main entry point to "inksprout.app.mjs" fulfills the migration to ECMAScript modules. Please verify that the file inksprout.app.mjs exists and is correctly implemented to avoid runtime import issues.

components/http/package.json (2)

3-3: Version Bump Update:
The version update to "0.5.1" looks appropriate for these changes. Ensure that this version bump follows the team's semantic versioning guidelines and is coordinated with any additional related package updates.

---

5-5: Main Entry Point Update:
Updating the main entry from "http.app.js" to "http.app.mjs" correctly aligns with the shift to ECMAScript modules. Please confirm that the ecosystem consuming this package is configured to support .mjs files to avoid any compatibility issues.

components/toggl/package.json (2)

3-3: Version Bump Updated
The version has been updated to "0.1.1" to reflect a new release. This is a standard minor version bump. Ensure that this change is aligned with your versioning strategy and that any downstream consumers are aware of the update.

---

5-5: Main Entry Point Updated to ESM Module
Changing the main field from "toggl.app.js" to "toggl.app.mjs" is appropriate for transitioning to ECMAScript modules. Verify that your build and deployment processes (and any dependent code steps) support ESM modules to prevent future import issues.

components/squarespace/package.json (1)

3-3: Version Update Confirmation
The package version has been correctly bumped to "0.0.5", ensuring consistency with the intended patch release strategy.

components/demio/package.json (2)

3-3: Version Update Verified.
The package version has been correctly bumped from a previous version to "0.0.6", aligning with the project's release workflow.

---

5-5: Main Entry Point Adjustment.
The main field is now set to "demio.app.mjs", which properly reflects the shift to ES Module syntax and resolves the import issues described in the PR objectives.

components/sendgrid/package.json (2)

3-3: Version Bump Update
The version has been updated from "0.4.1" to "0.4.2", which correctly reflects the incremental changes made in this PR.

---

5-5: Main Entry Point Upgrade to ES Module
Changing the main entry point from "sendgrid.app.js" to "sendgrid.app.mjs" aligns with the move from CommonJS to ECMAScript modules and fixes the import issue. Please verify that the corresponding "sendgrid.app.mjs" file exists and is correctly implemented.

components/emailoctopus/package.json (2)

3-3: Version Bump is Correctly Applied
The version has been updated to "0.1.2," which is consistent with the intended patch update.

---

5-5: Main Entry Point Update Reflects ES Module Transition
The update from "emailoctopus.app.js" to "emailoctopus.app.mjs" clearly indicates the shift to ECMAScript modules. Please ensure that all consumers of this package are compatible with this change.

components/brex/package.json (2)

3-3: Bump Package Version
The package version has been updated to "0.1.1", which signifies a new release. Ensure that this version change is aligned with your project's changelog and semantic versioning practices.

---

5-5: Update Main Entry Point for ESM Transition
Changing the main entry point to "brex.app.mjs" aligns with the migration from CommonJS to ECMAScript modules. Please verify that the corresponding module file exists and that any consuming code or deployment configurations have been updated accordingly.

components/givebutter/package.json (2)

3-3: Version Bump Update.
The version has been updated to "0.3.6", which aligns with the changes implemented across similar components in this PR. Ensure that this follows your semantic versioning guidelines and that any dependent documentation or integrations are updated accordingly.

---

5-5: Main Entry Point Update.
The "main" field has been updated from "givebutter.app.js" to "givebutter.app.mjs", indicating the shift to using ES modules. Please verify that the module is exported correctly in ECMAScript format and that all corresponding documentation reflects this change.

components/you_need_a_budget/package.json (2)

3-3: Version Bump Updated Successfully!
The version has been correctly bumped from the old version (implicitly 0.1.1) to 0.1.2. This is in line with the intent to version the package after making key changes and should help with proper dependency management.

---

5-5: Main Entry Point Updated for ES Module Compliance!
The main field has been updated from "you_need_a_budget.app.js" to "you_need_a_budget.app.mjs", reflecting the transition to ECMAScript modules. This change should resolve the import issues described in the PR objectives and ensure smoother integration in Node.js code steps that use ES modules.

components/customer_io/package.json (2)

3-3: Version Bump Update

The version has been correctly updated from "0.3.6" to "0.3.7". This update is consistent with the other similar changes in the PR.

---

5-5: Main Entry Point Change

The main field now points to "customer_io.app.mjs", reflecting the transition from CommonJS to an ECMAScript module format. Please verify that the new entry point file (customer_io.app.mjs) exists and is properly configured for ES module usage.

components/strava/package.json (2)

3-3: Version Update Confirmed
The version bump from "0.3.5" to "0.3.6" properly reflects an update following the changes in the main entry point configuration. This helps in tracking the change in functionality related to the import fix.

---

5-5: Main Entry Point Correction
Changing "main": "strava.app.js" to "main": "strava.app.mjs" correctly fixes the reference to the proper ECMAScript module file, addressing the import issue described in the PR objectives. Please verify that the file strava.app.mjs exists and properly exports the required functionalities.

components/crove_app/package.json (2)

3-3: Version Update Confirmation
The version field has been correctly bumped to "2.0.3". Ensure that the semver update aligns with the changes introduced in this release and that any related documentation (e.g., CHANGELOG) is updated accordingly.

---

5-5: Main Entry Point Update Validation
The main entry point is updated to "crove_app.app.mjs", indicating a successful shift from CommonJS to ES Module syntax. Please verify that the referenced .mjs file exists and that all module import statements within the project have been updated to accommodate this change.

components/smtp2go/package.json (2)

3-3: Version Bump is Correctly Updated.
The version change from "0.0.4" to "0.0.5" adheres to semantic versioning for this minor update.

---

5-5: Main Entry Point Update is Valid.
Updating the main entry from "dist/smtp2go.app.ts" to "dist/app/smtp2go.app.mjs" reflects the transition to ECMAScript modules and should address the previous import issues. Please ensure that the build process outputs the file at this new path.

components/repairshopr/package.json (2)

3-3: Version Bump Confirmation

The version field has been correctly updated to "0.0.3", indicating a new release. This change complies with the semantic versioning guidelines and properly signals downstream consumers about the update.

---

5-5: Main Entry Point Update to ES Modules

The main entry point has been updated from "repairshopr.app.js" to "repairshopr.app.mjs". This change aligns the component with ECMAScript module standards and should resolve the import issues previously encountered. Please ensure that the corresponding .mjs file exists and is properly implemented.

components/superdocu/package.json (2)

3-3: Package Version Bump Confirmed

The version has been updated to "0.0.3", which aligns with the incremental release strategy. Please ensure that the corresponding changelog and any documentation referencing the version are updated accordingly.

---

5-5: Updated Main Entry Point Verification

The main entry point has been updated from "superdocu.app.js" to "superdocu.app.mjs", correctly reflecting the shift to ECMAScript modules. Please verify that the new file exists and contains valid ESM syntax to prevent import issues in code steps.

components/zonka_feedback/package.json (2)

3-3: Version Update Verified
The version bump to "0.0.6" is consistent with the change objectives. Please ensure that any related release notes or changelog entries are updated accordingly.

---

5-5: Main Entry Point Correction
Switching the "main" entry from "zonka_feedback.app.js" to "zonka_feedback.app.mjs" correctly resolves the import issues and aligns with the shift to ECMAScript modules. Confirm that the corresponding file exists and that downstream consumers have been updated to reflect this change.

components/zoom_admin/package.json (2)

3-3: Version Update Confirmation.
The version update from "0.7.2" to "0.7.3" is consistent with the coordinated version bump across related components. This helps maintain semantic consistency in your package releases.

---

5-5: Main Entry Point Modification.
Changing the "main" value to "zoom_admin.app.mjs" correctly reflects the migration to ECMAScript modules. Please ensure that the "zoom_admin.app.mjs" file exists and that any related documentation or consumers of this component are updated accordingly.

components/microsoft_onedrive/package.json (2)

3-3: Version Update Confirmed.
The version update from "1.6.1" to "1.6.2" is correctly applied, consistent with the component's versioning scheme.

---

5-5: Main Entry Point Transitioned to ES Modules.
Changing the main entry point from "microsoft_onedrive.app.js" to "microsoft_onedrive.app.mjs" correctly reflects the move to ECMAScript modules. Please verify that the referenced microsoft_onedrive.app.mjs file exists and is properly configured.

components/teamgate/package.json (1)

3-3: Version Bump Update Confirmed.
The version change from "0.0.2" to "0.0.3" is correctly incremented and aligns with our coordinated release strategy. Ensure that the changelog and release notes reflect this update.

components/ecwid/package.json (2)

3-3: Version Bump Verified.
The version number has been updated to "0.0.11", which aligns with the release strategy. Please ensure that the changelog or release documentation is updated accordingly.

---

5-5: Updated Main Entry Point.
Changing the main field from "dist/ecwid.app.mjs" to "ecwid.app.mjs" suggests that the main module file now resides at the repository root, rather than within the dist directory. Verify that the build and distribution process has been adjusted to accommodate this new file location.

components/seventodos/package.json (2)

3-3: Version Bump is Correct.
The version has been incremented to "0.0.4", ensuring that changes to the package are properly versioned for releases.

---

5-5: Main Entry Point Update to ES Modules.
Changing the main entry point from "seventodos.app.js" to "seventodos.app.mjs" correctly reflects the transition from CommonJS to ES modules and resolves the import issue affecting the package. Please verify that the file "seventodos.app.mjs" exists and is properly configured.

components/stormboard/package.json (2)

3-3: Version Bump Update.
The version has been updated from "0.0.2" to "0.0.3", which is appropriate for releasing these changes. Please ensure that any related changelog or release notes are updated accordingly.

---

5-5: Main Entry Point Switch to ES Modules.
Changing the main entry point from "stormboard.app.js" to "stormboard.app.mjs" reflects the move to ECMAScript modules. Make sure that the corresponding file exists and that downstream consumers are aware of the module type change to avoid import issues.

components/spondyr/package.json (2)

3-3: Version Update to "0.0.4"
The version bump from "0.0.3" to "0.0.4" appropriately signals a change tied to the module format update. Please ensure that any downstream integration or CI/CD pipeline configurations referencing this version are updated, too.

---

5-5: Main Entry Point Update to ES Module Format
Updating the main entry from "spondyr.app.js" to "spondyr.app.mjs" correctly aligns this package with ECMAScript modules. Confirm that the file spondyr.app.mjs exists and that all consumers of the package are prepared to handle ES modules.

components/bandwidth/package.json (1)

5-5: Ensure Main Entry Point Update is Correct

The main field has been updated from its previous value to "bandwidth.app.js", which should resolve the import issues described in the PR. Please verify that the file bandwidth.app.js exists and is intended for this component. Additionally, note that other similar components are transitioning to an .app.mjs extension; confirm that keeping .app.js for the Bandwidth component is deliberate to avoid any module format inconsistencies.

components/orbit/package.json (2)

3-3: Version Update Applied Correctly

The version has been incremented from "0.0.1" to "0.0.2", which is in line with our versioning strategy for minor updates. Please ensure that dependent components are aligned if they reference this version.

---

5-5: Main Entry Point Update for ES Module Transition

The main file reference has been updated from "orbit.app.js" to "orbit.app.mjs", reflecting the shift to ECMAScript module syntax. Verify that the new "orbit.app.mjs" file exists and is correctly configured to support the ES module standard.

components/miestro/package.json (2)

3-3: Version Bump Update Looks Good
The version has been appropriately updated to "0.0.2" in line 3. This aligns with the overall release process and ensures that any consumers of the package are aware of the update.

---

5-5: Main Entry Point Updated to ECMAScript Module
The update to the main entry point ("miestro.app.mjs") correctly reflects a transition to ECMAScript modules. Please verify that the new file exists in the repository and that consumers using the package are configured to handle the .mjs extension.

components/basecamp/package.json (1)

3-5: Version and Main Field Update Confirmed

The version bump to "0.2.1" and the change of the main entry point from "basecamp.app.js" to "basecamp.app.mjs" correctly align with the migration to ECMAScript modules. This update should resolve the import issues previously encountered.

components/amazon_ses/package.json (1)

3-5: Consistent ES Module Transition

Updating the version to "0.3.7" and switching the main file from "amazon_ses.app.js" to "amazon_ses.app.mjs" is in line with the broader ES module migration effort. Ensure that any documentation or code steps referencing the old file name are updated accordingly.

components/algolia/package.json (1)

3-5: Accurate Version Increment and Main Field Adjustment

The changes update the version to "0.1.1" and modify the main entry from "algolia.app.js" to "algolia.app.mjs", which is consistent with the PR objectives. This helps ensure that consumers will correctly import the package using ECMAScript module semantics.

components/raindrop/package.json (1)

3-5: Standardized Module Format and Version Update

The update to version "0.3.14" and the new main entry "raindrop.app.mjs" properly reflect the migration from CommonJS to ES modules. This change should resolve previous issues with package imports. Verify that any integrations expecting the old path are revised accordingly.

components/pointagram/package.json (1)

5-5:

❓ Verification inconclusive

Main Entry Point Update
The main file has been updated from "pointagram.app.js" to "pointagram.app.mjs" to support ECMAScript modules. Verify that all consumers of this package update their import references accordingly and that this change aligns with your project’s module strategy.

---

I'm generating a shell script to help verify that no lingering references to the old main file (pointagram.app.js) remain in the codebase. This will confirm that consumers have been updated to use the new entry point (pointagram.app.mjs).

---

🏁 Script executed:

#!/bin/bash
# Search the entire repository for any references to the old main file name.
rg "pointagram\.app\.js"

Length of output: 26

---

Main Entry Point Confirmation
The package’s main entry was successfully updated from "pointagram.app.js" to "pointagram.app.mjs" to support ECMAScript modules. A repository-wide search for "pointagram.app.js" returned no results, suggesting that any outdated import references have been removed. Please manually verify that all consumers—both internal and external—are now importing "pointagram.app.mjs" and that the new file exists in the expected location within the components/pointagram directory.

components/refersion/package.json (3)

3-3: Version Bump Update Confirmation

The version has been updated from "0.0.5" to "0.0.6", which is appropriate to signal these changes. Please verify that any dependencies or consumers of this package are aware of the bumped version.

---

3-5: Ensure Consistent Integration Across the Codebase

Double-check that all related build configurations and package consumers now reference the ES module file correctly, eliminating any mismatches due to the file extension change. This consistency is crucial for smooth package imports.

---

5-5:

✅ Verification successful

Main Entry Point Update to ES Modules

The "main" field now points to "refersion.app.mjs", reflecting the transition from CommonJS to ECMAScript modules. Ensure that the actual file (refersion.app.mjs) is implemented using proper ES module syntax (e.g., using export/import instead of module.exports/require).

---

Below is a shell script you can run to verify that the file referenced by the "main" field exists and uses ES module syntax:

---

ES Module Main Entry Point Verification

The "main" field in components/refersion/package.json now points to "refersion.app.mjs", marking the transition from CommonJS to ES modules. Please ensure that:

• The file components/refersion/refersion.app.mjs exists.
• It correctly uses ES module syntax (i.e. uses import/export rather than require/module.exports).

---

🏁 Script executed:

#!/bin/bash
# Verify that `components/refersion/refersion.app.mjs` exists and employs ES module syntax.

FILE="components/refersion/refersion.app.mjs"

echo "Checking for file: $FILE"
if [ -f "$FILE" ]; then
    echo "File found: $FILE"
    echo "Searching for ES module syntax markers (import/export)..."
    grep -E "(import |export )" "$FILE" || echo "No explicit ES module syntax markers found in $FILE"
else
    echo "Error: File not found at $FILE"
fi

Length of output: 589

---

ES Module Update Verified: Main Entry Point in package.json

• The "main" field now points to "refersion.app.mjs" as expected.
• Verification confirms that components/refersion/refersion.app.mjs exists and uses ES module syntax (evidenced by import { axios } ... and export default).

No further refactoring is required.