import-maps (supported via "imports" in package.json) improve developer ergonomics, not performance. Node still resolves the mapped path normally; there’s no measurable “boost.”
They’re helpful to replace ugly relative imports, but they don’t change Node’s lookup speed.
Aliases in vite.config.js tell Vite (and its dev server/bundler) how to resolve imports during build and dev time. They don’t make runtime faster because your bundled output already contains resolved paths.
No, they say end-to-end, meaning they use raw obsevations. Most or all other medium-range models start with ERA5.
There's a paper from Norway that tried end-to-end, but their results were not spectacular. That's the aim of many though, including ECMWF. Note that ECMWF already has their AIFS in production, so AI weather prediction is pretty mainstream nowadays.
Google has a local nowcast model that uses raw observations, in production, but that's a different genre of forecasting than the medium-range models of Aardvark.
> Google has a local nowcast model that uses raw observations, in production, but that's a different genre of forecasting than the medium-range models of Aardvark.
It's very clear from the MetNet announcement blog[1] that they require HRRR or other NWP output at runtime.
reply