license-checker VS moment

I thought that was a fairly weird question. A couple of our APIs run on Ubuntu, which contains GNU software. He has access to our source code, and I had also previously sent him the output of license checker so he really should have been able to answer this himself.

NPM License Checker

I don't care whether it's all in one file or in a dozen files, but I want all of that information to be available programmatically in a text file (unlike in a readme or on Github) in a standardized location in a project.

In that respect, package.json is a strict win. Your lack of willingness to use `git blame` to see why you added a line, or lack of reasonable git comments, is not to be blamed on the file.

Complexity is unavoidable. How could you write a tool like license-checker [1] for a Go-based project without having license information in a standardized location? Without the scripts section, how can you create a tool like husky [2] that automatically installs git hooks for a project? Every single part of package.json is there for a good reason; at best you could argue that putting some of it in other files would be aesthetically superior, but that's just bikeshedding.

Complexity isn't de facto bad. Some complexity is required if you want a certain level of functionality to become available. Deno (and Go) are slowly accumulating that "cruft" as people realize that those functions are actually useful or even critical to a mature ecosystem.

[1] https://www.npmjs.com/package/license-checker

[2] https://www.npmjs.com/package/husky

Yes, all npm packages are supposed to have a valid SPDX license identifier, and there is an easy way to recursively check these values

For JavaScript I always used davglass/license-checker as a starting point but it's not being maintained anymore. Then I did similar things for the backend code, put everything together and sent it to the legal and security teams. At some point I thought "There must be a better way!". So, I started building sbomx about one and a half years ago. It's working fine enough to show it to the world and gather some feedback.

Check this package https://www.npmjs.com/package/license-checker

Good doctors and drivers make mistakes, too, and they still face liability for those mistakes.

I think that if your company is large enough, you should have employees, or pay someone, to mirror your dependencies and automate license checks. There are projects that do the latter already[1][2]. You can loop your lawyers in if licenses change to ensure you don't violate them. If (A)GPL code still ships in proprietary products, that's a process problem that the company needs to solve.

[1] https://github.com/dhatim/python-license-check

[2] https://github.com/davglass/license-checker

license-checker - Check licenses of your app's dependencies.

If you don't know what licenses you're currently using, I suggest the license-checker NPM tool.

Also, your IT dept is not entirely without concern here, you should be ensuring that you're not violating any open source licenses in your project, and be using something like https://www.npmjs.com/package/license-checker or an equivalent license checking service in your project language to ensure that everything is kosher

Moment.js lets you do amazing things with dates and times in JavaScript. You can easily compare, change, and format them in different ways. For example, you can say things like "today is Monday" or "3 hours ago" or "12/31/2020". To start with Moment.js, you need to install it and import it into your JavaScript project. For example:

To learn more about Moment.js, please visit their official website.

Ah, Moment.js, the guardian angel of date and time manipulation. Ever needed to format a date, calculate durations, or display something like "2 days ago"? Moment.js has got your back. It's a lifesaver for anything date and time-related, making it a must-have in your project, especially if you're into making your users feel like you really get them.

After hours of trying to figure out why Jekyll was still showing "Today" for a post I modified last week, I remembered that I am using the timeago filter from jekyll-timeago plugin. I was rendering the dates using {{ doc.last_modified_at | timeago }}. As you know, Jekyll is a static site generator, and it renders this as HTML at the time of build, and only then. This means any date rendered with timeago is hardcoded as is in the HTML and won't change until the next build. I switched all the dates to the "%-d %b %y" format for now. Might use moment.js in the future to get the timeago dates back.

moment: Handles date and time manipulations with ease. Learn more

For the longest time working with dates in JavaScript was a huge pain. That’s why libraries such as moment.js or date-fns are so popular. A lot of times I’d reach for these libraries when working with relative time formatting, but since late last year we’ve had pretty great browser support for the RelativeTimeFormat() method. In my mind, relative dates are just more visually appealing, especially for working with dates internationally. Dates like "5 days ago" or "in 2 months" are far more intuitive for users than 12/12/2023, or 03/11/2027. Folks in the US will see that as March 11, 2027, whereas the rest of the world will see that as November 03, 2027. What a nightmare.

İ am using moment js for a long time. You can check it also. https://momentjs.com/

We could control the DST flip by setting the test's input time to the appropriate time of year (summer/winter). However we couldn't control the timezone. We had to adjust the expected data in the test 🤢 using the same library which the production code used (momentjs).

8. Moment.js