bug: the `npx` command doesn't work
The following command should work
npx @tailcallhq/tailcall init
npm error could not determine executable to run
npm error A complete log of this run can be found in: /Users/tushar/.npm/_logs/2024-08-14T15_29_24_044Z-debug-0.log
0 verbose cli /Users/tushar/.nvm/versions/node/v20.15.1/bin/node /Users/tushar/.nvm/versions/node/v20.15.1/lib/node_modules/npm/bin/npm-cli.js
1 info using [email protected]
2 info using [email protected]
3 silly config:load:file:/Users/tushar/.nvm/versions/node/v20.15.1/lib/node_modules/npm/npmrc
4 silly config:load:file:/Users/tushar/Documents/Projects/type-tango/.npmrc
5 silly config:load:file:/Users/tushar/.npmrc
6 silly config:load:file:/Users/tushar/.nvm/versions/node/v20.15.1/etc/npmrc
7 verbose title npm exec @tailcallhq/tailcall init
8 verbose argv "exec" "--" "@tailcallhq/tailcall" "init"
9 verbose logfile logs-max:10 dir:/Users/tushar/.npm/_logs/2024-08-14T15_28_01_970Z-
10 verbose logfile /Users/tushar/.npm/_logs/2024-08-14T15_28_01_970Z-debug-0.log
11 silly logfile start cleaning logs, removing 1 files
12 silly logfile done cleaning log files
13 http fetch GET 200 https://registry.npmjs.org/@tailcallhq%2ftailcall 406ms (cache revalidated)
14 verbose stack Error: could not determine executable to run
14 verbose stack at getBinFromManifest (/Users/tushar/.nvm/versions/node/v20.15.1/lib/node_modules/npm/node_modules/libnpmexec/lib/get-bin-from-manifest.js:17:23)
14 verbose stack at exec (/Users/tushar/.nvm/versions/node/v20.15.1/lib/node_modules/npm/node_modules/libnpmexec/lib/index.js:183:15)
14 verbose stack at async module.exports (/Users/tushar/.nvm/versions/node/v20.15.1/lib/node_modules/npm/lib/cli/entry.js:74:5)
15 verbose pkgid @tailcallhq/[email protected]
16 verbose cwd /Users/tushar/Documents/Projects/type-tango
17 verbose Darwin 23.4.0
18 verbose node v20.15.1
19 verbose npm v10.7.0
20 error could not determine executable to run
21 verbose exit 1
22 verbose code 1
23 error A complete log of this run can be found in: /Users/tushar/.npm/_logs/2024-08-14T15_28_01_970Z-debug-0.log
/bounty $25
~~## 💎 $25 bounty • Tailcall Inc.~~
~~### Steps to solve:~~
~~1. Start working: Comment /attempt #2694 with your implementation plan~~
~~2. Submit work: Create a pull request including /claim #2694 in the PR body to claim the bounty~~
~~3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts~~
~~🙏 Thank you for contributing to tailcallhq/tailcall!~~ ~~🧐 Checkout our guidelines before you get started.~~ ~~💵 More about our bounty program.~~
| Attempt | Started (GMT+0) | Solution |
|---|---|---|
| 🔴 @Bhavyajain21 | Aug 14, 2024, 3:32:57 PM | WIP |
| 🔴 @Mubashirshariq | Aug 14, 2024, 4:37:08 PM | WIP |
| 🔴 @webbdays | Aug 21, 2024, 5:03:21 AM | WIP |
| 🔴 @Brihadeeshrk | Sep 1, 2024, 3:05:07 PM | WIP |
/attempt #2694
| Algora profile | Completed bounties | Tech | Active attempts | Options |
|---|---|---|---|---|
| @Bhavyajain21 | 4 tailcallhq bounties + 11 bounties from 2 projects |
TypeScript, Rust, JavaScript & more |
Cancel attempt |
/attempt #2694
| Algora profile | Completed bounties | Tech | Active attempts | Options |
|---|---|---|---|---|
| @Mubashirshariq | 1 bounty from 1 project | JavaScript, TypeScript, HTML |
Cancel attempt |
[!NOTE] The user @Bhavyajain21 is already attempting to complete issue #2694 and claim the bounty. We recommend checking in on @Bhavyajain21's progress, and potentially collaborating, before starting a new solution.
@Bhavyajain21: Reminder that in 1 days the bounty will become up for grabs, so please submit a pull request before then 🙏
@Mubashirshariq: Reminder that in 1 days the bounty will become up for grabs, so please submit a pull request before then 🙏
The bounty is up for grabs! Everyone is welcome to /attempt #2694 🙌
/attempt #2694
| Algora profile | Completed bounties | Tech | Active attempts | Options |
|---|---|---|---|---|
| @webbdays | 4 tailcallhq bounties | Python, Rust, HTML & more |
Cancel attempt |
@webbdays: Reminder that in 1 days the bounty will become up for grabs, so please submit a pull request before then 🙏
The bounty is up for grabs! Everyone is welcome to /attempt #2694 🙌
@tusharmath
@Brihadeeshrk: Reminder that in 1 days the bounty will become up for grabs, so please submit a pull request before then 🙏
@webbdays The latest version throws this error —
npx --verbose @tailcallhq/tailcall init
npm verbose cli /Users/tushar/.nvm/versions/node/v20.15.1/bin/node /Users/tushar/.nvm/versions/node/v20.15.1/lib/node_modules/npm/bin/npm-cli.js
npm info using [email protected]
npm info using [email protected]
npm verbose title npm exec @tailcallhq/tailcall init
npm verbose argv "exec" "--loglevel" "verbose" "--" "@tailcallhq/tailcall" "init"
npm verbose logfile logs-max:10 dir:/Users/tushar/.npm/_logs/2024-09-26T08_19_20_356Z-
npm verbose logfile /Users/tushar/.npm/_logs/2024-09-26T08_19_20_356Z-debug-0.log
npm http fetch GET 200 https://registry.npmjs.org/@tailcallhq%2ftailcall 310ms (cache revalidated)
npm verbose stack Error: could not determine executable to run
npm verbose stack at getBinFromManifest (/Users/tushar/.nvm/versions/node/v20.15.1/lib/node_modules/npm/node_modules/libnpmexec/lib/get-bin-from-manifest.js:17:23)
npm verbose stack at exec (/Users/tushar/.nvm/versions/node/v20.15.1/lib/node_modules/npm/node_modules/libnpmexec/lib/index.js:183:15)
npm verbose stack at async module.exports (/Users/tushar/.nvm/versions/node/v20.15.1/lib/node_modules/npm/lib/cli/entry.js:74:5)
npm verbose pkgid @tailcallhq/[email protected]
npm verbose cwd /Users/tushar/Documents/Projects/tailcall
npm verbose Darwin 23.4.0
npm verbose node v20.15.1
npm verbose npm v10.7.0
npm error could not determine executable to run
npm verbose exit 1
npm verbose code 1
npm error A complete log of this run can be found in: /Users/tushar/.npm/_logs/2024-09-26T08_19_20_356Z-debug-0.log
looking into it.
@tusharmath can i know the package version this code was deployed.
I think new package is not published.
version: 0.115.0 doesn't have new installation scripts
@tusharmath any issue publishing new package.
https://github.com/tailcallhq/tailcall/releases/download/vv0.115.3/tailcall-x86_64-unknown-linux-gnu
while deploying version is used as v0.115.3 instead of 0.115.3
const specific_url = v${version}/tailcall-${targetPlatform.get("target")}${targetPlatformExt}
A step to test npm package before publish is good to have. To avoid affecting users.
Action required: Issue inactive for 30 days. Status update or closure in 7 days.
Issue closed after 7 days of inactivity.