wry | Cross-platform WebView library in Rust for Tauri | Android library

What happens is that you produce your built app but not bundle it (using the --directory flag).

Therefore you have extra JS files in your file structure.

And in your attempts, they are mixed with your Meteor project structure, in a build folder (when you use command meteor build build --directory) or directly merged (meteor build .. --directory).

Therefore, on the next build run, Meteor picks these extra JS files as if they were part of your source code (eager loading), and fails, as suggested in the warning message:

The output directory is under your source tree. Your generated files may get interpreted as source code! Consider building into a different directory instead meteor build ../output

It would have worked in your next attempt if you had specified an explicit sibling build folder, instead of just the parent folder (which therefore puts files directly in your Meteor project root), e.g. meteor build ../siblingFolder

Another possible workaround is to use a build folder name starting with a dot ., so that Meteor ignores it on the next runs when it looks for source code, e.g. meteor build ./.build

See special directories docs:

The following directories are also not loaded as part of your app code:

• Files/directories whose names start with a dot, like .meteor and .git