Issue 1:
Build failing with:

ninja: Entering directory `C:\denodev\deno\target\debug'
[43/633] LINK flatc.exe flatc.exe.pdb
FAILED: flatc.exe flatc.exe.pdb
ninja -t msvc -e environment.x64 -- ../../third_party/llvm-build/Release+Asserts/bin/lld-link.exe /nologo /OUT:./flatc.exe /PDB:./flatc.exe.pdb @./flatc.exe.rsp
lld-link: error: duplicate symbol: bool const std::_Is_integral<bool> in obj/build_extra/flatbuffers/flatc/flatc_main.obj and in obj/build_extra/flatbuffers/compiler_files/cpp_generator.obj
lld-link: error: duplicate symbol: bool const std::_Is_integral<char> in obj/build_extra/flatbuffers/flatc/flatc_main.obj and in obj/build_extra/flatbuffers/compiler_files/cpp_generator.obj
lld-link: error: duplicate symbol: bool const std::_Is_integral<signed char> in obj/build_extra/flatbuffers/flatc/flatc_main.obj and in obj/build_extra/flatbuffers/compiler_files/cpp_generator.obj
lld-link: error: duplicate symbol: bool const std::_Is_integral<unsigned char> in obj/build_extra/flatbuffers/flatc/flatc_main.obj and in obj/build_extra/flatbuffers/compiler_files/cpp_generator.obj
lld-link: error: duplicate symbol: bool const std::_Is_integral<wchar_t> in obj/build_extra/flatbuffers/flatc/flatc_main.obj and in obj/build_extra/flatbuffers/compiler_files/cpp_generator.obj
lld-link: error: duplicate symbol: bool const std::_Is_integral<char16_t> in obj/build_extra/flatbuffers/flatc/flatc_main.obj and in obj/build_extra/flatbuffers/compiler_files/cpp_generator.obj
lld-link: error: duplicate symbol: bool const std::_Is_integral<char32_t> in obj/build_extra/flatbuffers/flatc/flatc_main.obj and in obj/build_extra/flatbuffers/compiler_files/cpp_generator.obj
lld-link: error: duplicate symbol: bool const std::_Is_integral<short> in obj/build_extra/flatbuffers/flatc/flatc_main.obj and in obj/build_extra/flatbuffers/compiler_files/cpp_generator.obj
lld-link: error: duplicate symbol: bool const std::_Is_integral<unsigned short> in obj/build_extra/flatbuffers/flatc/flatc_main.obj and in obj/build_extra/flatbuffers/compiler_files/cpp_generator.obj
lld-link: error: duplicate symbol: bool const std::_Is_integral<int> in obj/build_extra/flatbuffers/flatc/flatc_main.obj and in obj/build_extra/flatbuffers/compiler_files/cpp_generator.obj
lld-link: error: duplicate symbol: bool const std::_Is_integral<unsigned int> in obj/build_extra/flatbuffers/flatc/flatc_main.obj and in obj/build_extra/flatbuffers/compiler_files/cpp_generator.obj
lld-link: error: duplicate symbol: bool const std::_Is_integral<long> in obj/build_extra/flatbuffers/flatc/flatc_main.obj and in obj/build_extra/flatbuffers/compiler_files/cpp_generator.obj
lld-link: error: duplicate symbol: bool const std::_Is_integral<unsigned long> in obj/build_extra/flatbuffers/flatc/flatc_main.obj and in obj/build_extra/flatbuffers/compiler_files/cpp_generator.obj
lld-link: error: duplicate symbol: bool const std::_Is_integral<__int64> in obj/build_extra/flatbuffers/flatc/flatc_main.obj and in obj/build_extra/flatbuffers/compiler_files/cpp_generator.obj
lld-link: error: duplicate symbol: bool const std::_Is_integral<unsigned __int64> in obj/build_extra/flatbuffers/flatc/flatc_main.obj and in obj/build_extra/flatbuffers/compiler_files/cpp_generator.obj
lld-link: error: duplicate symbol: bool const std::_Is_floating_point<float> in obj/build_extra/flatbuffers/flatc/flatc_main.obj and in obj/build_extra/flatbuffers/compiler_files/cpp_generator.obj
lld-link: error: duplicate symbol: bool const std::_Is_floating_point<double> in obj/build_extra/flatbuffers/flatc/flatc_main.obj and in obj/build_extra/flatbuffers/compiler_files/cpp_generator.obj
lld-link: error: duplicate symbol: bool const std::_Is_floating_point<long double> in obj/build_extra/flatbuffers/flatc/flatc_main.obj and in obj/build_extra/flatbuffers/compiler_files/cpp_generator.obj
lld-link: error: duplicate symbol: bool const std::is_void_v<void> in obj/build_extra/flatbuffers/flatc/flatc_main.obj and in obj/build_extra/flatbuffers/compiler_files/cpp_generator.obj
lld-link: error: duplicate symbol: bool const std::is_void_v<void const> in obj/build_extra/flatbuffers/flatc/flatc_main.obj and in obj/build_extra/flatbuffers/compiler_files/cpp_generator.obj
lld-link: error: too many errors emitted, stopping now (use /errorlimit:0 to see all errors)
[48/633] CC obj/build_extra/rust/ring-core/cpu-intel.obj
ninja: build stopped: subcommand failed.

Issue 2:
Okay, this project looks really interesting so far. While watching the talk I just noticed one thing that might be a problem for some developers. That's just allowing imports with relative path's (besides URLs). There are a lot of questions on the internet on how one can import a file in TS/Webpack/whatever relative to the project root. With relative paths people will end up with things like import { foo } from '../../../../modules/featureA/foo.ts'. Or was it just ../../../modules/...? What if I move my files around? Yes, you have to update your imports anyway. But figuring out how many directories you have to go up is a very tedious task on its own.

In the talk, you/Ryan talked about browser compatibility. I haven't tried out ES modules in the browser just yet. But I'm pretty sure it also supports absolute paths. Absolute in that context means relative to the web root. It would be really handy if we were able to just write import { foo } from '/modules/featureA/foo.ts'.

Of course, now there's the question: What is the root directory of a deno application? The only thing that makes sense to me right now is the folder that contains the entry file ‒ basically what process.cwd() is in node. But I also think it's fine to place the entry file in the most top-level directory of the project, isn't it?

Or is there any problem about absolute paths I didn't think about so far? What do you think about that?