WASM Splitting issue using #[lazy_routes]

[davidcpp-ython]

Describe the bug
Hello. I started implementing lazy_routes into my app, but I am encountering this OS error that states :

0: Error emitting Chunk { splits: ["lazy_admin_view_5754084777364687109", "lazy_documents_view_18258890327090950471", "lazy_financial_reporting_compliance_documentation_viewer_view_10606121879465236070", "lazy_user_management_administration_dashboard_view_12859904693686961530"], hash: "" } at /Users/davidilasi/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/cargo-leptos-0.2.42/src/wasm_split_tools/emit.rs:905:43
   1: File name too long (os error 63)

This happens particularly on release mode (while working on ARM Mac, not sure if this really helps).

Here is a demo app I created that simulates the environment and how it fails: https://github.com/davidcpp-ython/issue-leptos-wasm-split

Next Steps

• I will make a PR
• I would like to make a PR, but need help getting started
• I want someone else to take the time to fix this
• This is a low priority for me and is just shared for your information
  Additional context
  Add any other context about the problem here.

[links234]

I tested on WSL (Ubuntu) and it's the same problem.

[gbj]

Just based on the file name being too long I assume it's the same as this issue, right? leptos-rs/cargo-leptos#556

There is a proposed solution there if you're interested in experimenting and making a PR. The WASM-splitting code all lives in that repo in any case.

[gbj]

You can test leptos-rs/cargo-leptos#559. I was not able to reproduce the issue using the example provided but the PR should truncate these kinds of filenames.

[gbj]

Oh interesting -- just saw your note about release mode. I was able to reproduce it in release mode... I wonder why the names would be different. In any case, the updated cargo-leptos CLI in the PR linked above does seem to fix the issue.

[davidcpp-ython]

Super, thanks for helping me with this issue!

[davidcpp-ython]

@gbj oh sorry, but I forgot to mention this bug happens in debug (sometimes if u have too many lazy_routes with long filenames...). What I presented to you is only failing on release, but on my real app I also came across this case when debug fails. But probably your fix should catch this problem too.