overengineeringstudio / overengineeringstudio/effect-utils

notion schema generate-config: external .ts config can't resolve workspace deps under packaged binary

Open
#895 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area:notion system:notion-cli type:bug
Dominant language
TypeScript
Stars
82
Forks
2
Avg merge
1d 8h
Merged PRs (30d)
121

Description

Problem

The standalone notion binary loads an external notion-schema-gen.config.ts at runtime, but its resolver can't reach transitive @overeng/* deps. A config that imports @overeng/notion-cli/config (the defineConfig / file helpers) fails because those helpers pull in workspace packages the packaged resolver can't find:

Cannot find module '@overeng/effect-path' from config-def.ts

Only a plain-object config (using node:-builtin imports only) loads under the packaged binary. The same config works when run under bun from source.

Expected

The packaged notion binary should resolve transitive @overeng/* deps when loading an external .ts config, so defineConfig / file helper configs work from the standalone binary too.

Package: packages/@overeng/notion-cli (src/config-def.ts, src/config.ts).

Posted on behalf of @schickling
field value
agent_name 💜 cl1-violet
agent_session_id 5ce468e2-a077-44ee-a724-bca1fb992e1c
agent_tool Claude Code
agent_tool_version 2.1.202
agent_runtime Claude Code 2.1.202
agent_model claude-opus-4-8
runtime_profile /nix/store/34v4ljmkjh4sgzax68wwgggmzf69zmfk-coding-agent-runtime-profile/share/coding-agents/profile.json
skills_manifest /nix/store/92pwq9mx1byj8nl9an05dyh4baykvf1d-agent-skills-corpus/share/agent-skills/manifest.json
worktree effect-utils/schickling/2026-07-07-notion-demo
machine mbp2025
tooling_profile dotfiles@unknown

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in packages/@overeng/notion-cli/src/config-def.ts and src/config.ts, then reproduce the failure by loading an external notion-schema-gen.config.ts with the packaged notion binary. Trace how the packaged resolver handles the config's transitive @overeng/* imports. Done means configs using defineConfig and file resolve successfully in the standalone binary, matching source execution.

Written by the indexing model from the issue text.

Assessment

Tech stack
bun, typescript
Domain
cli, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.