✨ MAJOR FEATURES: • Auto-zoom intelligence với smart bounds fitting • Enhanced 3D GPS markers với pulsing effects • Professional route display với 6-layer rendering • Status-based parking icons với availability indicators • Production-ready build optimizations 🗺️ AUTO-ZOOM FEATURES: • Smart bounds fitting cho GPS + selected parking • Adaptive padding (50px) cho visual balance • Max zoom control (level 16) để tránh quá gần • Dynamic centering khi không có selection 🎨 ENHANCED VISUALS: • 3D GPS marker với multi-layer pulse effects • Advanced parking icons với status colors • Selection highlighting với animation • Dimming system cho non-selected items 🛣️ ROUTE SYSTEM: • OpenRouteService API integration • Multi-layer route rendering (glow, shadow, main, animated) • Real-time distance & duration calculation • Visual route info trong popup 📱 PRODUCTION READY: • SSR safe với dynamic imports • Build errors resolved • Global deployment via Vercel • Optimized performance 🌍 DEPLOYMENT: • Vercel: https://whatever-ctk2auuxr-phong12hexdockworks-projects.vercel.app • Bundle size: 22.8 kB optimized • Global CDN distribution • HTTPS enabled 💾 VERSION CONTROL: • MapView-v2.0.tsx backup created • MAPVIEW_VERSIONS.md documentation • Full version history tracking
1.9 KiB
import/unambiguous
Warn if a module could be mistakenly parsed as a script by a consumer leveraging
Unambiguous JavaScript Grammar to determine correct parsing goal.
Will respect the parserOptions.sourceType from ESLint config, i.e. files parsed
as script per that setting will not be reported.
This plugin uses Unambiguous JavaScript Grammar internally to decide whether
dependencies should be parsed as modules and searched for exports matching the
imported names, so it may be beneficial to keep this rule on even if your application
will run in an explicit module-only environment.
Rule Details
For files parsed as module by ESLint, the following are valid:
import 'foo'
function x() { return 42 }
export function x() { return 42 }
(function x() { return 42 })()
export {} // simple way to mark side-effects-only file as 'module' without any imports/exports
...whereas the following file would be reported:
(function x() { return 42 })()
When Not To Use It
If your application environment will always know via some other means how to parse, regardless of syntax, you may not need this rule.
Remember, though, that this plugin uses this strategy internally, so if you were
to import from a module with no imports or exports, this plugin would not
report it as it would not be clear whether it should be considered a script or
a module.