Alexander Wunschik

> ... Not working with setOptions method. Maybe we should fix this?

I propose to use [dayjs](https://day.js.org/) instead of moment.js in the future. Dayjs has a good support for locals and is very small. An alternative would be to use native date...

I would suggest the following procedure: - find all the places moment is used. (Here [eslint-plugin-you-dont-need-momentjs](https://www.npmjs.com/package/eslint-plugin-you-dont-need-momentjs#eslint-plugin) can help) - replace all moment-operations with functions from the [DateUtil](https://github.com/visjs/vis-timeline/blob/master/lib/timeline/DateUtil.js). If functions are...

Instead on just using dayjs we could introduce a neutral adapter layer. Similar of what [chart.js is doing with their "adapters"](https://github.com/chartjs/awesome#adapters). That way people could choose an adapter with a...

[date-io](https://github.com/dmtrKovalenko/date-io) looks really promising. It looks like it does not support tree-shaking, but that is maybe a price we should pay!? merge-requests welcome!

It looks like [both axis example](https://visjs.github.io/vis-timeline/examples/graph2d/05_bothAxis.html) is also not functining correctly at the moment. @bakobence Thanks for reporting this!

@AlexDM0 Hi :smiley: Looks like the project is missing a maintainer (again) :disappointed:

> When will this be merged to master? : I don't have time to work on this at the moment, but I really would love to get rid of moment.js!...

Maybe somebody wants to create a new example that demonstrates this? I also would love this!

The easiest way to solve this is to switch to the `peer` build: ```js import { DataSet } from 'vis-data/peer'; import { Edge, Network, Node, Options } from 'vis-network/peer'; ```