Tree Not Generated

[jeffreystorer]

After selecting the root file, I see only that file, with no tree. The file bubble has only a link to open the file.

I get the same behavior with react apps created with CRA and Vite.

[MichaelBenliyan]

Hello Jeffrey!
Thanks for reaching out. Not sure why you're experiencing those issues. It's hard to debug without more specific information regarding the files that are giving you this issue. There might be something we've overlooked in our parsing system that is making it not find the child components in the JSX/TSX files you're talking about. Would be happy to provide more help if you can provide more info.
Best

[jeffreystorer]

https://github.com/jeffreystorer/tlcgolf-vite-js/tree/master/src Neither main.jsx nor App..jsx generates a tree. Nor do the files in the pages folder. Thanks.

On Tue, Feb 28, 2023 at 06:50 Michael Benliyan ***@***.***> wrote: Hello Jeffrey! Thanks for reaching out. Not sure why you're experiencing those issues. It's hard to debug without more specific information regarding the files that are giving you this issue. There might be something we've overlooked in our parsing system that is making it not find the child components in the JSX/TSX files you're talking about. Would be happy to provide more help if you can provide more info. Best — Reply to this email directly, view it on GitHub <#29 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADGVZMOZTMPI2RMTXGEO5NDWZXQ7HANCNFSM6AAAAAAVJUQD5Y> . You are receiving this because you authored the thread.Message ID: ***@***.***>

--

…

__________________ Jeffrey B. Storer 617-279-6140 (Mobile) ***@***.*** 53 Peregrine Crossing Savannah, GA 31411 912-335-1565 (Home) 610-646-2337 (Fax)

[MichaelBenliyan]

Good morning Jeffrey!
Thank you for providing the repo you are experiencing this issue in. After forking and testing it out, I see the problem you are facing. The issue is actually coming from ReacTree currently not supporting absolute imports (the imports starting with '@'). If those imports are modified to be with the older style of './components/...' then it will work. Thank you for bringing this to our attention. I will update this thread when ReacTree supports absolute imports.
Hope this helped clear things up.
Best

[jeffreystorer]

Thanks. I assumed that was the problem. I have the same issue in the repo tlcgolf, which is CRA project using absolute imports: https://github.com/jeffreystorer/tlcgolf Jeffrey B. Storer 617-279-6140 mobile ***@***.*** 53 Peregrine Crossing Savannah, GA 31411-2863 912-335-1565

…

On Tue, Feb 28, 2023 at 11:19 AM Michael Benliyan ***@***.***> wrote: Good morning Jeffrey! Thank you for providing the repo you are experiencing this issue in. After forking and testing it out, I see the problem you are facing. The issue is actually coming from ReacTree currently not supporting absolute imports (the imports starting with '@'). If those imports are modified to be with the older style of './components/...' then it will work. Thank you for bringing this to our attention. I will update this thread when ReacTree supports absolute imports. Hope this helped clear things up. Best — Reply to this email directly, view it on GitHub <#29 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADGVZMJP5N3MFZUH34IYFO3WZYQR3ANCNFSM6AAAAAAVJUQD5Y> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[ptim]

I have this issue also, in a vite react-ts project using root-relative imports.

I will update this thread when ReacTree supports absolute imports.

I didn't spot anything in the README about this issue - it would be great to mention there... I also wondered if react-router is supported, but didn't find a mention of that either.

My abbr config:

// tsconfig.json
{
  "compilerOptions": {
    "baseUrl": "./src"
    // ...
  }
}

// vite.config.ts
export default defineConfig(({ mode }) => {
  const baseConfig = {
    base: '',
    plugins: [
      react(),
      // allows vite and vitest to resolve TS path config (eg 'baseUrl')
      tsconfigPaths(),
    ],
    // ...
  }
  return baseConfig
})

// main.ts
import { Button } from 'components';

// ...