New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cannot install via npm #104
Comments
the bundled scripts are "scripts": {
"test": "echo \"no tests for now\"",
"_postinstall": "husky install",
"prepack": "pinst --disable",
"postpack": "pinst --enable",
"lint": "npx eslint . --ext .ts,.tsx,.js,.jsx --cache --fix",
"build": "tsc && vite build",
"prepublishOnly": "npm run build"
}, I don't think this will cause install husky |
could you please give me the full logs? |
Hmm, where can i upload it. I'll paste the relevant last part of logs
|
I believe I've removed the postinstall script before publishing. Could you please check node_modules/@textea/json-viewer, and give me the screenshot of files and details of its packages.json |
I had to install it using npm install --ignore-scripts, otherwise i never got the node_modules here's package json
|
maybe i know the reason, let me publish a patch after lunch |
hold on, are you using husky in your project? |
Hi, yes, we use it for linting in the same way as your project does. Other members can install without a problem, but i'm using gitkraken and i guess it doesn't create a .git file |
then I think might that because your configuration. Could you re-setup husky in your project? https://typicode.github.io/husky/#/?id=automatic-recommended |
Refs: typicode/husky#851 |
the only code we have in our .husky is
I don't know why it's calling your pre-commit command :/ |
In my release code, there's no pre-commit command in the files |
no clue why it wants to run: |
let me see if there're related issues in upstream |
could you please try 2.9.1? |
I've remove all |
I think it's not out yet
|
npm cache clean --force |
Aaand that worked! |
I get the following error:
Can husky be excluded from the packaged dist 🙏
The text was updated successfully, but these errors were encountered: