Getting a lot of errors when following the contribution documentation

[shannonhochkins]

Getting a lot of errors when following the contribution documentation

[yann510]

I'm running PopOS 22 (linux) with node 18 and npm 9

[shannonhochkins]

I've just updated the contributing docs - sorry mate, i missed a vital step.

Because of the complexities with @hakit/core, storybook uses the distributable files from @hakit/core, so to kick off storybook, you must have a built version of @hakit/core

npm run build:core

Then you should be able to run npm start and load up the storybook instance.

I haven't quite solved this problem yet, and do be honest it really shouldn't be that difficult to fix, i simply haven't gotten around to it yet!

If you're working on a new feature with @hakit/core, what i normally do is cd into the core directory, and run npm run watch:build, then in a separate terminal, i run npm start and then you can work in tandom.

Also, storybook has a complete replica of the authentication and websocket flow, if you want to test against your home assistant instance there's a few solutions

1. replace @hass-connect-fake with @hakit/core in the storybook stories
2. Follow the steps here: https://github.com/shannonhochkins/ha-component-kit/blob/master/CONTRIBUTING.md#prep-for-local-development-with-a-test-dashboard

Hope this helps!

[yann510]

I have been using NX for the past few years to solve these types of problems: https://github.com/nrwl/nx
You should take a look at it :)

If it's something that interests you and would be beneficial for the project, I will help get you to get it up and running.

When I'm trying to build from a fresh master, I'm getting the following error now:

> @hakit/[email protected] build:sync-script-cli
> tsup

CLI Building entry: scripts/sync-user-types/cli.ts
CLI Using tsconfig: tsconfig.json
CLI tsup v7.2.0
CLI Using tsup config: /home/yann510/github/ha-component-kit/packages/core/package.json
CLI Target: es5
CLI Cleaning output folder
ESM Build start
Error: Bindings not found.
    at Compiler.<anonymous> (/home/yann510/github/ha-component-kit/node_modules/@swc/core/index.js:225:19)
    at Generator.next (<anonymous>)
    at /home/yann510/github/ha-component-kit/node_modules/@swc/core/index.js:34:71
    at new Promise (<anonymous>)
    at __awaiter (/home/yann510/github/ha-component-kit/node_modules/@swc/core/index.js:30:12)
    at Compiler.transform (/home/yann510/github/ha-component-kit/node_modules/@swc/core/index.js:202:16)
    at Object.transform (/home/yann510/github/ha-component-kit/node_modules/@swc/core/index.js:344:21)
    at Object.renderChunk (/home/yann510/github/ha-component-kit/node_modules/tsup/dist/index.js:2008:32)
    at /home/yann510/github/ha-component-kit/node_modules/tsup/dist/index.js:1912:53
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

[shannonhochkins]

I'll take a look at it tomorrow!

Can I ask what version of node / npm you're using?

After you first reported, I did checkout a clean repository and it did run through fine, so this may be environment specific

[shannonhochkins]

Also, what operating system?

[shannonhochkins]

Have you tried this solution? vitejs/vite-plugin-react-swc#74

Hopefully, it's just as simply as removing the lock file then running npm install again

[yann510]

Awesome, running npm i -D @swc/cli @swc/core fixed it for me, I'll create a PR.

[shannonhochkins]

Awesome, running npm i -D @swc/cli @swc/core fixed it for me, I'll create a PR.

Interesting!

What OS are you using? Obviously it works for me without installing these packages, just curious to know the differences between our setups, would you also mind letting me know your node / npm version?