Skip to content

fix(linear,slack): point exports to dist/, add ./path-mapper subpath#20

Merged
khaliqgant merged 1 commit intomainfrom
fix/adapter-linear-slack-exports
Apr 16, 2026
Merged

fix(linear,slack): point exports to dist/, add ./path-mapper subpath#20
khaliqgant merged 1 commit intomainfrom
fix/adapter-linear-slack-exports

Conversation

@khaliqgant
Copy link
Copy Markdown
Member

@khaliqgant khaliqgant commented Apr 16, 2026

Summary

Same fix as #19 (adapter-github), applied to adapter-linear and adapter-slack:

  • exports field now points to dist/*.js instead of src/*.ts — Turbopack cannot handle raw .ts files from node_modules
  • Added ./path-mapper subpath export for zero-dependency path computation functions
  • files field changed to ["dist"] so compiled output is published (not raw source)

Both path-mapper.ts modules are fully self-contained with zero external imports.

Test plan

  • npm run build succeeds for both packages
  • adapter-linear tests pass (13/13)
  • adapter-slack tests pass (8/8)
  • cloud nango-sync-relayfile tests pass (9/9) with these package versions installed locally

🤖 Generated with Claude Code


Open with Devin

Same fix as adapter-github PR #19:
- exports field now points to dist/*.js instead of src/*.ts
- Added ./path-mapper subpath export for zero-dep path computation
- files field changed to ["dist"] so compiled output is published

Fixes Turbopack "Unknown module type" errors in Next.js consumers
that can't handle raw .ts source files from node_modules.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@khaliqgant khaliqgant merged commit c24fcf9 into main Apr 16, 2026
1 check passed
Copy link
Copy Markdown

@devin-ai-integration devin-ai-integration Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 2 additional findings.

Open in Devin Review

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5e3295fab0

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines 18 to 20
"files": [
"src"
"dist"
],
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Add prepare build for dist-only package contents

Publishing only dist here makes git/file installs fragile because this package has no prepare script to generate dist before packing. prepublishOnly runs for npm publish, but it does not run when users install directly from a Git URL or local path, so the tarball can end up with just package.json and imports then fail at runtime with missing ./dist/*.js files.

Useful? React with 👍 / 👎.

Comment on lines 19 to 21
"files": [
"src",
"tsconfig.json"
"dist"
],
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Add prepare build for dist-only package contents

This change has the same packaging regression as linear: with files restricted to dist and no prepare hook, installs from Git/local sources do not build artifacts before pack time. In those environments prepublishOnly is skipped, so consumers can receive a package without dist/index.js and hit module resolution failures immediately.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant