René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"`intent` bin conflicts with @tanstack/intent and imports removed subpath","articleBody":"### TanStack Devtools version\n\nv0.14.2\n\n### Framework/Library version\n\nReact v19.2.8; Node v24.20.0; Npm v11.19.0\n\n### Describe the bug and the steps to reproduce it\n\nWhen installing the package dependencies in my project that include both `@tanstack/intent` and `@tanstack/devtools`, I've found there is a collision between these two package's bin outputs. They both define `\"bin\": { \"intent\": \"...\" }` in their respective `package.json`, but `@tanstack/devtools`'s bin output (implemented at [bin/intent.js](https://github.com/TanStack/devtools/blob/main/bin/intent.js)) tries to import `'@tanstack/intent/intent-library'` which results in a `ERR_PACKAGE_PATH_NOT_EXPORTED` error as this export path was removed from `@tanstack/intent` (there is a reference to the Intent issue below).\n\nIn both my React project and in the minimum reproducible example provided, running `npm ci`/`npm i` resolves `node_modules/.bin/intent` to the bin output from `@tanstack/devtools` rather than `@tanstack/intent`. Another engineer on my team sees this same behaviour, but another engineer can correctly resolve `@tanstack/intent`'s bin at `node_modules/.bin/intent`.\n\n**Reproducible steps** \nIn the minimum reproducible example there is a simple node project which has two dependencies (intent and devtools).\n1. Install the dependencies in the minimum reproducible example project\n2. Run `npm run help`\n\nThe `node_modules/.bin/intent` resolves to devtool's, then running `npm run help` executes `intent help` and because the incorrect `intent` bin is installed, an `ERR_PACKAGE_PATH_NOT_EXPORTED` error is thrown.\n\n[Intent issue #143](https://github.com/TanStack/intent/issues/143) removed `intent-library` from `@tanstack/intent`'s exports.\n> Breaking: anything invoking intent-library directly must move to the normal intent discovery flow. No compatibility shim.\n\n### Your Minimal, Reproducible Example - (Sandbox Highly Recommended)\n\nhttps://github.com/zlo120/intent-bin-min-repro-example/tree/main\n\n### Screenshots or Videos (Optional)\n\n_No response_\n\n### Do you intend to try to help solve this bug with your own PR?\n\nYes, I think I know how to fix it and will discuss it in the comments of this issue\n\n### Terms & Code of Conduct\n\n- [x] I agree to follow this project's Code of Conduct\n- [x] I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.","author":{"url":"https://github.com/zlo120","@type":"Person","name":"zlo120"},"datePublished":"2026-09-04T05:17:43Z","url":"https://github.com/TanStack/devtools/issues/525"}