Owen Waller

> [@owenwaller](https://github.com/owenwaller) would it work to just add a -syscall-js or similar option to vugugen, and how about also -gen-suffix. For example: > > The defaults would be the same...

Hi @Dadido3 *Aside: I'm going to break my reply into three parts. Hopefully that will make it easier to respond to.* First some comments on the test structure. > I...

@Dadido3 Now some comments about the build tags. *Aside: regardless of what I am about to say, I still believe the that the directory structure change I have outlined in...

@Dadido3 And part three.... > Also, just as a sidenote: I'm working on a new vugu/js package which will fix https://github.com/vugu/vugu/issues/328 and possibly > all other problems which have arised...

@Dadido3 ```go func runGoTestInModuleDir(module moduleData) error { f := func() error { return goCmdV("test", "-v", filepath.Join(module.name, "testdriver")) } return runFuncIn(module, f) } ``` No, we can't do this. If you...

@Dadido3 > I reevaluated most of my pain points i had with using //go:build js && wasm in vugu components (and its generated files) and came to the conclusion that...

@Dadido3 @bradleypeabody Having seen [this comment form Bradley on Issue #328](https://github.com/vugu/vugu/issues/328#issuecomment-2614669212) things appear to be a little more subtle. Looking at things I think we might need to be even...

@Dadido3 It's a very small point but it might make my point clearer. If you try to execute the following lines of code on a native platform ```go import (...

There has been considerable discussion on this issue in PR #332. Please see there for the details. This has resulted in PR #336 which brings together the proposed fix from...

@Dadido3 > I had never thought about that as a solution. A simple sub-directory for the test won't work however. It needs a sub-module I think because the `mage` based...