Unknown file extension ".css"

[dillionverma]

Unknown file extension ".css"

[dillionverma]

I added a commit which triggers this issue here

magicuidesign/magicui@0b127bb

[zce]

Based on your description, it seems that this has nothing to do with Velite.

Anyway, I will try to reproduce the problem you mentioned first.

[zce]

I think I know what the problem is.

I need some time to see if there is a better solution.

[dillionverma]

a similar issue also occurred with another component in the registry which I completely removed called "wavy-dot-pattern" and these issues didn't occur with contentlayer which led me to believe it was something to do with the way velite is bundling / rendering the markdown

[zce]

Yes, the reason is that I stopped bundling third-party libraries in the velite.config.ts in a previous version, which is different from contentlayer

#62

Please wait for me for a moment

[zce]

A brief explanation of the cause of the problem: In the reference files of velite.config.ts, some modules not intended for the Node.js runtime were imported using dynamic import, and these imports are unrelated to the operation of Velite.

However, the esbuild used internally by Velite tries to bundle and execute these modules, which are not for the Node.js runtime, leading to the issue.

Although Velite can ignore the bundling of these modules by specifying esbuild's external configuration option, like this: external: ["@/registry"], I believe this is not a common scenario, so I don't plan to support custom external. For detailed reasons, refer to #62.

I personally think there are two solutions to this problem:

1. Remove the dynamic import from the relevant files: magicuidesign/magicui#190
2. Prepare a separate configuration module for the rehype plugin, but this requires keeping the files in sync, so it's not recommended.

Since the original codebase seems to be missing some files, the PR is not yet complete. If you agree with my view, I can try to improve it when I have time.

[dillionverma]

thanks for prompt responses!

i took a quick look at the PR and think it should theoretically work

I also prefer option 1 instead of having to maintain the two separate files

tried to test locally but noticed specific pages weren't running

im not too familiar with the lower level details lazy components yet - any idea what might be going on here?

[zce]

Note my usage in PR:

const Component = lazy(() => import(`@/registry/components/examples/${component}`))

You cannot extract this path into a variable, as this will prevent the compiler from finding it properly.

[zce]

@dillionverma If there are no more questions, I will close this issue.