You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5-16Lines changed: 5 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
# Tide predictor
4
4
5
-
A Javascript tide harmonic calculator.
5
+
A tide harmonic calculator written in TypeScript.
6
6
7
7
<!-- START DOCS -->
8
8
@@ -25,17 +25,6 @@ yarn add @neaps/tide-predictor
25
25
26
26
```
27
27
28
-
## Importing
29
-
30
-
You can import the module using Ecmascript, or CommonJS. Note that the CommonJS export is transpiled, so deep debugging the module that way will be difficult.
There are also packaged and minified versions for the browser in `dist/web`.
38
-
39
28
# Usage
40
29
41
30
Neaps requires that you [provide your own tidal harmonics information](#constituent-object) to generate a prediction.
@@ -44,7 +33,7 @@ Because many constituent datum come with multiple phases (in the case of NOAA's
44
33
45
34
Note that, for now, Neaps **will not** do any timezone corrections. This means you need to pass date objects that align with whatever timezone the constituents are in.
46
35
47
-
```javascript
36
+
```typescript
48
37
importTidePredictorfrom'@neaps/tide-predictor'
49
38
50
39
const constituents = [
@@ -83,7 +72,7 @@ The returned tide prediction object has various methods. All of these return reg
83
72
84
73
Returns the predicted high and low tides between a start and end date.
If you want predictions for a subservient station, first set the reference station in the prediction, and pass the [subservient station offests](#subservient-station) to the `getExtremesPrediction` method:
0 commit comments