Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Casing in NPM @clerk/backend-core is broken, breaking the package on Linux

See original GitHub issue

Review the documentation: https://docs.clerk.dev/
Search for existing issues: https://github.com/clerkinc/javascript/issues
Go through package changelog files.
[N/A] Provide the Frontend API key from your application dashboard.

Package + Version

@clerk/clerk-js
@clerk/clerk-react
@clerk/nextjs
@clerk/remix
@clerk/clerk-expo
@clerk/backend-core
@clerk/clerk-sdk-node
@clerk/edge
other:

Version:

1.14.1

Description

It would appear that backend-core contains an incorrectly cased import. This completely breaks anything that depends on it on any case-sensitive file system.

When using clerk-sdk-node on Linux, for example, the error:

Error: Cannot find module './ClerkBackendApi'

Is returned. Digging into this further, it seems that the file is named “ClerkBackendAPI.js” in the npm tarball:

tar xvzf backend-core-1.14.1.tgz
...
x package/dist/cjs/api/ClerkBackendAPI.js
x package/dist/mjs/api/ClerkBackendAPI.js
x package/dist/cjs/api/ClerkBackendAPI.d.ts
x package/dist/mjs/api/ClerkBackendAPI.d.ts
...

Now, macos and Windows have default case insensitive filesystems, so the package works fine, which makes this a real surprise when your application suddenly stops working after moving it into a Docker container.

Running the build locally, it seems all the files are properly named:

npm notice 1.7kB   dist/cjs/api/ClerkBackendApi.d.ts                                
npm notice 1.5kB   dist/cjs/api/ClerkBackendApi.d.ts.map                            
npm notice 4.6kB   dist/cjs/api/ClerkBackendApi.js

So I’m not quite sure how they got renamed like that in the NPM tarball.