Any plan to replace "request" and "moment"?

[cowboysdude]

@0m4r meh either way LOL

[BKeyport]

@cowboysdude Been playing with changing over anyway (to luxon), and all I’ve been able to do for sure is make MM not come up at all.

There needs to be MUCH better documentation on how to build out with external modules. It don’t make sense.

[sdetweil]

@bkeyport explain more. externals are used in node_helper, and some can be used in module name.js as loaded by getScripts()

if the lib shows useage as a < script … />
link, then u can use it in getScripts

[BKeyport]

@sdetweil I’m trying to get luxon up and running.

Supports Node.js 6+. Install via NPM:

npm install --save luxon

const { DateTime } = require("luxon");

Do I need to use node_helper to get it going, then?

https://moment.github.io/luxon/#/install

[sdetweil]

@bkeyport require only works in node_helper

the doc also gives u a < script approach

still npm install
then getScripts to load the file from node_modules folder/luxon folder

the use in modulename.js as shown for browser

[BKeyport]

@sdetweil Oh, so I set up the require in node_helper, and use it accordingly in the main module script? Nice.

[sdetweil]

@bkeyport no. one OR the other

[BKeyport]

@sdetweil OK, I’m lost.

If Moment goes away, I’ll delete my modules.

[sdetweil]

@bkeyport if you don’t have a node_helper, the you use the getScripts approach

if u have both, then u have to do both

[BKeyport]

@sdetweil

I give up.

Suggestion for the main app -

Create a date-time service that hides what library you’re using. If you decide to replace the library in the future, you’ll need to update only one file.

That way, we don’t have to move at all - just convert from accessing moment directly to accessing the internal service.

In the meantime, I’m indeed dropping it.