Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Web Front-End Stack is Ancient #1504

Closed
ctm opened this issue Oct 18, 2024 · 2 comments
Closed

Web Front-End Stack is Ancient #1504

ctm opened this issue Oct 18, 2024 · 2 comments
Assignees
Labels
chore Maintenance or other non-bug, non-feature wontfix This will not be worked on

Comments

@ctm
Copy link
Owner

ctm commented Oct 18, 2024

Research alternatives and switch from yarn dev and yarn build.

Our front-end stack started using webpack via yarn on March 4th, 2020 or earlier. That is no longer a recommended way of doing things and probably hasn't been for years. That is probably why the new default use of reference types isn't biting other developers, but it is biting us (#1503).

In researching how to disable reference types, I tried to find a repo for whatever template that I used to get started to see how it's been updated to address this issue and four years in the Rust wasm ecosystem is like a decade or more. My guess is I should simply start at the wasm-pack home page and go from there.

I use trunk for proof-of-concept work, so I should look at it too. However, searching for npm in the Trunk Guide produces no hits, so I don't know how I'd glue in uikit and dragee, neither of which I can remove quickly.

I'm starting this one out with easy, but I won't really know until I explore more. We don't currently do anything particularly strange AFAIK, but there's a lot to forget in four years.

@ctm ctm added chore Maintenance or other non-bug, non-feature high priority Should be done fairly soon easy Trivial to do (even when tired!) and semi-worthwhile labels Oct 18, 2024
@ctm ctm self-assigned this Oct 18, 2024
@ctm
Copy link
Owner Author

ctm commented Oct 18, 2024

Ugh.

The wam-pack guide points to rust-webpack-template which itself is older than my stack. It uses npm instead of yarn, but yarn is/was a more modern (but npm-compatible) package manager than npm. Underneath, it's probably invoking the same node modules which will presumably fail due to reference types and will (again, presumably) have the same inscrutability problem w.r.t. disabling reference types.

Furthermore, I looked at trunk some more and in addition to not finding a way to integrate node modules, there doesn't appear to be a way to turn SVG files into data-uris. In fact, from my perspective, it looks like various asset building aspects of trunk that had been discussed in 2020 haven't turned into a general purpose solution.

I'll probably hop on the Yew discord and ask around to see if there's anyone out there like myself who uses wam-pack and can't figure out how to turn off reference types.

@ctm
Copy link
Owner Author

ctm commented Oct 18, 2024

I did a bunch of searching on the Yew discord and didn't see anyone running into the problem and very few people using wasm-pack. I think the bug reporting that I'm going to be doing as part of #1503 is the best way to proceed.

@ctm ctm closed this as completed Oct 18, 2024
@ctm ctm added wontfix This will not be worked on and removed high priority Should be done fairly soon easy Trivial to do (even when tired!) and semi-worthwhile labels Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Maintenance or other non-bug, non-feature wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

1 participant