Is there a recommended way to use node modules?

[l-monninger]

I'm considering how much of a hard break from an existing Vue application a move to Yew would be. We use several JavaScript clients that don't have comps in Rust yet. Ultimately, we might be moving away from these clients as part of a larger reorg, but it would obviously be optimal to not have to roll our own in the meantime.

I'm aware of two ways to interoperate:

1. Creating externs manually.
2. Using the js! macro from stdweb.

Would there be any other way to do this that is better for Yew? I saw this on crates. Is it recommended?

Non-yew question: if there isn't a better way to work with Yew, I'm leaning towards stdweb. As far as developer experience is concerned, is there a way to make the Rust linter treat those js! macros with eslint?

[l-monninger]

I'm considering how much of a hard break from an existing Vue application a move to Yew would be. We use several JavaScript clients that don't have comps in Rust yet. Ultimately, we might be moving away from these clients as part of a larger reorg, but it would obviously be optimal to not have to roll our own in the meantime.

I'm aware of two ways to interoperate:

1. Creating externs manually.
2. Using the js! macro from stdweb.

Would there be any other way to do this that is better for Yew? I saw this on crates. Is it recommended?

Non-yew question: if there isn't a better way to work with Yew, I'm leaning towards stdweb. As far as developer experience is concerned, is there a way to make the Rust linter treat those js! macros with eslint?

@WorldSEnder You know anything about this?

[WorldSEnder]

The js-wasm interop should be simple, even without any whistles wasm_bindgen is already sufficiently powerful to do most things. For example, you can import functions from existing js snippets or other namespaces.

That being said, finding a way to make two encompassing frameworks interoperate will probably not be simple. I don't know so much about Vue, but both Yew and Vue would expect to be in charge of the DOM and most likely interfere with each other if you run them on one page. Which leaves you with the commitment to convert all components before being able to switch, and again I can't really tell how much work that would be coming from Vue.

If you have a small application sitting around that you can try the conversion on, give it a shot.

---

Now to address your questions, specifically

I'm aware of two ways to interoperate:

Creating externs manually.

Use wasm_bindgen, it's really good for creating those, it even includes some necessary js glue code in the generated files.

Using the js! macro from stdweb.

Haven't really needed stdweb in yew. Putting js in js files would be my stylistic preference (see js snippets link above). The reason I prefer bindgen rn is that it can do do a bunch of tricks, like getting caching functions from the prototype instead of each time from the instance, with small changes to the consuming code.

Would there be any other way to do this that is better for Yew? I saw this on crates. Is it recommended?

yew-interop is for deferring the loading of external resources needed in your yew components. @Madoshakalaka can surely explain it better than I can :)