Upcoming Major Changes (v7)

[Eonasdan]

I want to keep track of some major changes I'm considering for the next major release. For a timeline, see #2730.

• Removing the dist folder.
  JsDeliver can point to the npm version, and npm allows for referencing GitHub branches directly.
  I'm not sure about CDN JS. They pick up changes to the repo and pull in the built files.
  The npm package already includes the plugins and locales, however the nuget packages do not.
• Removing the types folder.
  This will still be in the npm and nuget packages, just not checked in anymore.
• Remove deprecated code
  - [ ] useTwentyfourHours. This was changed to localization.hourCycle instead.
  - [ ] Remove customDateFormat plugin (rolled into the main code base)
• Remove sub/unsub functionality. The element event listeners are good enough, and these ended up being confusing.
• Guess components based on format provided and drop those options
• Fix file naming convention
• Fix any function name convention (look for use of private, _, etc.)
• Remove or reduce Intl usages. It's just too limited.

---

• Move to Floating UI.
  Popperjs is transforming into Floating UI. Currently, the picker allows for overwriting of the popperjs usage.

Bootstrap will probably migrate with BS 6. I will likely not migrate to floating ui until Bootstrap does. Even though the picker is not dependent on BS, it is still widely used with BS and I don't want to add unnecessary dependency burdens to devs.

---

• Temporal API. I need to do a POC using Temporal first, but from what I've seen so far, the native Date object will be superseded by Temporal. The picker's DateTime will likely be replaced by Temporal meaning that all date functions will only accept/emit Temporal instances.

[ururk]

I manage some legacy apps and don't like to use a CDN, having the dist folder all ready to go is very helpful. But, I can always download from CDN JS - just one extra step.

[Eonasdan]

The files from the dist folder will still be in the npm package, they just won't be saved to the repo.

[lenamtl]

Not everone know how to make a build or use npm, having the file ready to use save a lot of time.
This is also an easy way for newbie to use it.
I don't see any good reason to remove the dist folder from a repo.

[Eonasdan]

The files will still be on the CDN. There will still be multiple ways of using it without the dist folder being committed to the repo itself.