Component folders not being created during install, all index.tsx files end up in src/components

[pdiegel]

During installation, the scaffolding step never creates the individual component directories under src/components. Instead, every component’s index.tsx is written directly into the root src/components folder, so they overwrite one another and only the last one remains.

[garrett-from-chainlift]

Steps to reproduce? 𝗚𝗮𝗿𝗿𝗲𝘁𝘁 𝗠𝗮𝗰𝗸 Founder, Chainlift • (714) 584-5371

…

On Mon, Jul 21, 2025, 6:25 AM Philip Diegel ***@***.***> wrote: *pdiegel* created an issue (Chainlift/liftkit#202) <#202> During installation, the scaffolding step never creates the individual component directories under src/components. Instead, every component’s index.tsx is written directly into the root src/components folder, so they overwrite one another and only the last one remains. — Reply to this email directly, view it on GitHub <#202>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXXQ7JTACKR2ONYHCC5E44T3JTS4NAVCNFSM6AAAAACB73HDDOVHI2DSMVQWIX3LMV43ASLTON2WKOZTGI2DQNRWGQYDINY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[pdiegel]

Steps to reproduce?

𝗚𝗮𝗿𝗿𝗲𝘁𝘁 𝗠𝗮𝗰𝗸
Founder, Chainlift • (714) 584-5371
…

Here are the exact steps I followed, straight from your website guide and YouTube walkthrough:

1. git clone https://github.com/Chainlift/liftkit-template.git
2. cd liftkit-template
3. npm install
4. npm run add all (tried individual components as well)

What I see:

• A single src/components/index.tsx file containing only the latest installed component’s code
• No per‑component subfolders created. All component .css files are within the root src/components dir

[garrett-from-chainlift]

Wild. Thanks for reporting. Will look into ASAP! 𝗚𝗮𝗿𝗿𝗲𝘁𝘁 𝗠𝗮𝗰𝗸 Founder, Chainlift • (714) 584-5371

…

On Mon, Jul 21, 2025, 8:09 AM Philip Diegel ***@***.***> wrote: *pdiegel* left a comment (Chainlift/liftkit#202) <#202 (comment)> Steps to reproduce? 𝗚𝗮𝗿𝗿𝗲𝘁𝘁 𝗠𝗮𝗰𝗸 Founder, Chainlift • (714) 584-5371 … <#m_3219842092184866078_m_2886728172429158801_> Here are the exact steps I followed, straight from your website guide and YouTube walkthrough: 1. git clone https://github.com/Chainlift/liftkit-template.git 2. cd liftkit-template 3. npm install 4. npm run add all (tried individual components as well) What I see: - A single src/components/index.tsx file containing only the latest installed component’s code - No per‑component subfolders created. All component .css files are within the root src/components dir — Reply to this email directly, view it on GitHub <#202 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXXQ7JWB46HTQWQYMHBMCQL3JT7AXAVCNFSM6AAAAACB73HDDOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAOJXGE3TINJRGE> . You are receiving this because you commented.Message ID: ***@***.***>

[0yassin]

after following the steps carefully (i tried both ways of installing):

• prompted to overwrite an index.tsx a lot of times and ending up with the components folder having one index.tsx, and all the .css files, y or n doesn't make a difference

• Module not found: Can't resolve '@chainlift/liftkit'
• "@/lib/css/index.css" (and many other files) doesn't exist

[garrett-from-chainlift]

And this is all after cloning the template project? 𝗚𝗮𝗿𝗿𝗲𝘁𝘁 𝗠𝗮𝗰𝗸 Founder, Chainlift • (714) 584-5371

…

On Mon, Jul 21, 2025, 1:30 PM 0yassin ***@***.***> wrote: *0yassin* left a comment (Chainlift/liftkit#202) <#202 (comment)> after following the steps carefully (i tried both ways of installing): - prompted to overwrite an index.tsx a lot of times and ending up with the components folder having one index.tsx, and all the .css files, y or n doesn't make a difference image.png (view on web) <https://github.com/user-attachments/assets/467c82cd-4888-43cb-8d77-907b09e2a859> - Module not found: Can't resolve ***@***.***/liftkit' - "@/lib/css/index.css" (and many other files) doesn't exist — Reply to this email directly, view it on GitHub <#202 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXXQ7JQW2WZNTKGZ6YNZDA33JVEXJAVCNFSM6AAAAACB73HDDOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAOJYGYZTMOBVGA> . You are receiving this because you commented.Message ID: ***@***.***>

[0yassin]

yes exactly

[garrett-from-chainlift]

We're looking into it now. 𝗚𝗮𝗿𝗿𝗲𝘁𝘁 𝗠𝗮𝗰𝗸 Founder, Chainlift • (714) 584-5371

…

On Mon, Jul 21, 2025, 2:15 PM 0yassin ***@***.***> wrote: *0yassin* left a comment (Chainlift/liftkit#202) <#202 (comment)> yes exactly — Reply to this email directly, view it on GitHub <#202 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXXQ7JV2SBW7MVYD772QBXD3JVJ6BAVCNFSM6AAAAACB73HDDOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAOJZGAZDQMZVGQ> . You are receiving this because you commented.Message ID: ***@***.***>

[JeremiahSecrist]

would you be willing to push your repo up that has this error? I'm unable to reproduce this issue on my machine.

[JeremiahSecrist]

• Would you be willing to record the steps taken (from scratch) to show the issue in action?
• Use https://asciinema.org/ to record the session.
• Be sure to run node --version during the setup process.

[pdiegel]

• Would you be willing to record the steps taken (from scratch) to show the issue in action?
• Use https://asciinema.org/ to record the session.
• Be sure to run node --version during the setup process.

I believe this issue might be Windows‑specific:

• WSL (Ubuntu 24.04.2 LTS, Node v22.17.1, npm v11.4.2)
  The installer correctly creates each component folder and the respective index.tsx.
  Recording: https://asciinema.org/a/ntaR5P0DSuPkkrOugDiPlKrP8

• Native Windows (PowerShell, Node v22.17.1, npm v11.4.2)
  Every component’s index.tsx ends up merged into src/components/index.tsx instead of its own folder.
  Asciinema doesn't seem to be supported in windows so if there is another way of capturing the issue that you would like to see, please let me know.

[JeremiahSecrist]

Now that I see you are running windows ill be sure to test against it. im working on an overhaul of the cli coming soon and ill be sure to test it against a windows vm. in the meantime can you use wsl?

[garrett-from-chainlift]

Update: We're running final QA on a patch that should solve the problem. Will notify here as well as in the next email newsletter when ready.

[garrett-from-chainlift]

@pdiegel @0yassin We just published the fix. Try again? https://www.npmjs.com/package/@chainlift/liftkit