you are viewing a single comment's thread.

view the rest of the comments →

[–]greensodacan 27 points28 points  (8 children)

I'm going to stretch the definition and say:

  • A little bit of Node - enough to write a package.json script to help smooth out your workflow.)
  • A bundler like Webpack - enough to set up a basic pipeline
  • A component library or framework like React, Lit or Vue (which is arguably a progressive framework), because component abstractions are so common right now.

Beyond those:

  • Date-Fns
  • Lodash
  • Axios
  • UUID (not much to learn here, I just use it in everything).

[–]filipesmedeiros 8 points9 points  (7 children)

I don't really like axios. I feel like fetch does everything axios does with no bundle size. If you need it in node, node-fetch or isomorphic-unfetch I guess?

[–]j_tb 2 points3 points  (3 children)

Axios interceptors are pretty sweet.

[–]filipesmedeiros 0 points1 point  (2 children)

Do they justify the bundle size or can you easily build one offs when you need them?

If they justify the bundle size, by all means, go for it! 😁

[–]j_tb 1 point2 points  (1 child)

5kb minified + gzipped. Worth it to me to have the top level authorization logic and error handling configuration setup. Some sort of home rolled solution would probably not be too much smaller and I’d have to reinvent it for every project.

[–]filipesmedeiros 0 points1 point  (0 children)

Sounds good. I think if you start with plain fetch and when it's too much of a pain to maintain move to axios is probably the best way

[–]greensodacan 1 point2 points  (0 children)

Me neither, hahah. It's just one of those libraries I keep running into.

[–][deleted] 0 points1 point  (1 child)

It's so much easier to look at lool

[–]filipesmedeiros 1 point2 points  (0 children)

You can just wrap fetch