Closed beaussan closed 4 months ago
@beaussan This looks like a broken build output (we create those package.json
fields in our build script). Could you check if this is still a problem with our latest version?
Closing as this should now be fixed for future releases by #517. Let me know if it reoccurs.
What happened?
While I was trying to use the project, I followed the readme.
First of all, I tried with the ts config file name, however it wasn't picked automatically (fixed by https://github.com/code-pushup/cli/issues/307 ), but then I was hit with the following error :
So I circle around the issue by changing the import to the following :
And that gave another error :
What would you expect to happen?
I expect typescript to be happy, node to resolve correctly and to be able to run the eslint plugin properly.
After following my hunch, I can confirm that the types of the packages are wrong (report here) :
I was able to make it work with the following minimal changes to the package.json in my node_module :
What steps did you take?
Follow the readme, install the eslint plugin, and run code-pushup. Pr that do this : https://github.com/beaussan/beaussan-mono/pull/127
What operation system are you on?
MacOS
Node version
v18.18.2
Relevant log output
No response