4 ms·
The proposal doesn't seem to take into account the versioning of the included modules. > import { Date } from "std:Date"; > import { Date } from "std:Date+2.1
by aboutruby 8y ago
The proposal doesn't seem to take into account the versioning of the included modules.
> import { Date } from "std:Date";
> import { Date } from "std:Date+2.1.6-alpha.1";
Which version is the first line going to include? Latest? First?
importmap for backward compatibility / polyfills is very neat though.
I would love to see lowdash/underscore included as a standard library.
- philipwalton 8y agoThis is not different from existing web APIs, which are also not versioned.
- nathan_long 8y ago...and this has always been a unique pain point of development in the browser.
- paxys 8y agoI assume whatever is shipped with the browser version it is running on.
- nikeee 8y agoDoes versioning imports imply that the browser has to ship with all versions of a stdlib Module?
- nathan_long 8y agoIt could instead imply "if the browser didn't ship with a version that satisfies my requirements, use the polyfill"
- LoSboccacc 8y agoif they want these libraries to ever be used as default they need to have a stable api, so it needs versioning and the ability to link to specific version or versions in a bracket and the backport of security fixes across releases within a reasonable timeframe why would anyone develop toward a library that doesn't provide those basic guarantees? there's also no guarantee that your web app gets deployed to an up to date browser, so it's either you can specify which api level your app wants or we're all back to specify which browser version an app runs onto.