analytics-utils: incorrect reference to cjs main entrypoint in 1.1.0

[real34]

What happens

When I install @analytics/core in my project, with analytics-utils 1.1.0 I get the following error:

> tmp-fc-test-skeleton-test-app@3.14.0 dev /tmp/fc-test-skeleton/test-app
> node --import tsx/esm ./server.mjs

node:internal/modules/cjs/loader:1437
  const err = new Error(`Cannot find module '${request}'`);
              ^

Error: Cannot find module '/tmp/fc-test-skeleton/test-app/node_modules/.pnpm/@analytics+core@0.12.17_@types+dlv@1.1.5/node_modules/analytics-utils/dist/analytics-utils.js'
    at createEsmNotFoundErr (node:internal/modules/cjs/loader:1437:15)
    at finalizeEsmResolution (node:internal/modules/cjs/loader:1426:15)
    at resolveExports (node:internal/modules/cjs/loader:657:14)
    at Function._findPath (node:internal/modules/cjs/loader:749:31)
    at node:internal/modules/cjs/loader:1387:27
    at m._resolveFilename (file:///tmp/fc-test-skeleton/test-app/node_modules/.pnpm/tsx@4.19.2/node_modules/tsx/dist/register-RyGUjI6j.mjs:1:789)
    at defaultResolveImpl (node:internal/modules/cjs/loader:1057:19)
    at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1062:22)
    at Function._load (node:internal/modules/cjs/loader:1211:37)
    at TracingChannel.traceSync (node:diagnostics_channel:322:14) {
  code: 'MODULE_NOT_FOUND',
  path: '/tmp/fc-test-skeleton/test-app/node_modules/.pnpm/@analytics+core@0.12.17_@types+dlv@1.1.5/node_modules/analytics-utils'
}

Expected

The app should start properly. It worked fine yesterday (i.e: with the previous version).

Analysis

The package.json still refers to dist/analytics-utils.js but when analyzing the packaged code it now is named dist/analytics-utils.cjs.

Should the main entrypoint be updated accordingly to prevent this issue?

💡 Other packages (such as @analytics/type-utils and @analytics/storage-utils) also seem impacted.

[shuckster]

Seeing the same.

[DavidWells]

This is why we can't have nice things!

I updated the mono-repo architecture and it looks like the newer microbuild is making .cjs files instead of .js ones

Working on a fix/release of all effected packages now.

[DavidWells]

ok I believe I've fixed all the file paths and I've added a verify build step to make sure lil stuff like this doesnt happen again.

These packages got bumped. Can you folks try installing again and see if this resolves your issue?

@analytics/core@0.13.1 or analytics@0.8.18

These were bumped

Successfully published:
 - @analytics/activity-utils@0.2.2
 - @analytics/cookie-utils@0.2.14
 - @analytics/core@0.13.1
 - @analytics/form-utils@0.3.15
 - @analytics/global-storage-utils@0.1.9
 - @analytics/listener-utils@0.4.2
 - @analytics/localstorage-utils@0.1.12
 - @analytics/original-source-plugin@1.0.15
 - @analytics/redact-utils@0.1.5
 - @analytics/remote-storage-utils@0.4.24
 - @analytics/scroll-utils@0.1.26
 - @analytics/session-storage-utils@0.0.9
 - @analytics/session-utils@0.2.4
 - @analytics/storage-utils@0.4.4
 - @analytics/type-utils@0.6.4
 - @analytics/url-utils@0.2.5
 - @analytics/visitor-source@0.0.9
 - analytics@0.8.18
 - analytics-utils@1.1.1

[jules-w2]

Hey @DavidWells 👋

I'm not 100% sure if this is the same root cause as the issue described here, but since version 0.8.17 (same behavior on 0.8.18), I'm getting this error when compiling my JS:

✘ [ERROR] Could not resolve "@analytics/core"
    node_modules/analytics/lib/analytics.browser.es.js:1:26:
      1 │ import { Analytics } from '@analytics/core';
        ╵                           ~~~~~~~~~~~~~~~~~
  You can mark the path "@analytics/core" as external to exclude it from the bundle, which will
  remove this error and leave the unresolved path in the bundle.
1 error

My setup is very minimal:

import Analytics       from "analytics"
import googleAnalytics from "@analytics/google-analytics"

document.addEventListener("DOMContentLoaded", () => {
    const analytics = Analytics({
      app:     document.documentElement.dataset.app,
      plugins: [
        googleAnalytics({
          measurementIds: [googleAnalyticsId]
        })
      ]
    })
    analytics.page()
})

This was working fine before 0.8.17 — nothing else in my build setup has changed.

Do you have any idea what might be causing this or if it's related to the recent changes in the package structure?

Thanks a lot 🙏

[DavidWells]

It's broken right now 🫠

Pin to previous working version.

Changing the build and mono repo setup is causing some issues I need to resolve

[Maybach91]

I’m currently maintaining my codebase and upgrade dependencies one after another (so no code change as well).
And I got a similar issue using vite watch (5.4.19):

 [commonjs--resolver] Failed to resolve entry for package "@analytics/core". The package may have incorrect main/module/exports specified in its package.json.

Maybe it’s because of this change.

The issue occurs in 0.8.17 as well as in 0.8.18.
0.8.16 is working fine. ✅

jfyi @DavidWells

[shuckster]

Upgraded to 0.8.19 and things appear to work, thank you!