We're updating the issue view to help you get more done. 

Determine a Strategy per Moment.js being a "Legacy Project"

Description

Moment.js is now considered a legacy project. It is being kept up for stability, but it is worth considering how we want to use it in the future and if we want to start using another library where we can (when there are solutions that include the ability to manage timezones)

Project Status from Moment.js: https://momentjs.com/docs/#/-project-status/

Slack Threads:
*https://tidepoolteam.slack.com/archives/C087MHT9R/p1600222972017500
*https://tidepoolteam.slack.com/archives/C087MHT9R/p1602249615015500

Article:
*https://dockyard.com/blog/2020/02/14/you-probably-don-t-need-moment-js-anymore

Also to be considered – how and where we use `sundial` and if we want to retire that library

Done Criteria

*Agreed upon strategy for managing dates across repos that currently use Moment.js

Design Specifications:

None

Accessibility Specifications

None

Test Strategy

None

Environment

None

New Fields for Analytics/Export Configuration (if needed)

None

Priority

None

Assignee

Unassigned

QA Assignee

None

Reporter

Thacher Hussain

Requested By (External)

None

Fix versions

None

T-Shirt Size

None

Risk Level

None

User Experience Assessment Level

None

UEA: Issue Volume

None

UEA: Category

None

Components

None

Design Review Required?

None

Design Approved By:

None

QA done during validation of another ticket?

None

Accessibility Review Required?

None

Accessibility Review Approved By

None

Approved for Production By:

None

Pull Request Needed

None

Resolved Build #

None
Configure