Add Cache-Control defaults to all the demo store routes

[blittle]

WHY are these changes introduced?

1. Update Remix to 1.14.0
2. Add Cache-Control defaults to all the demo store routes

WHAT is this pull request doing?

HOW to test your changes?

Post-merge steps

Checklist

• I've read the Contributing Guidelines
• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've added a changeset if this PR contains user-facing or noteworthy changes
• I've added tests to cover my changes

[frandiox]

What do you think about doing this instead?

Suggested change

	export const CACHE_SHORT = generateCacheControlHeader(CacheShort());
	export const CACHE_LONG = generateCacheControlHeader(CacheLong());
	export const CACHE_NONE = generateCacheControlHeader(CacheNone());
	export const HEADERS_CACHE_SHORT = Object.freeze({'Cache-Control': generateCacheControlHeader(CacheShort())});
	export const HEADERS_CACHE_LONG = Object.freeze({'Cache-Control': generateCacheControlHeader(CacheLong())});
	export const HEADERS_CACHE_NONE = Object.freeze({'Cache-Control': generateCacheControlHeader(CacheNone())});

Then, in loaders we can just use {headers: HEADERS_CACHE_SHORT} instead of typing "cache-control" everywhere.

[blittle]

Hmm, not a bad idea, though it makes it a bit more complex to extend and define a custom header

[wizardlyhel]

mmm .. I like what Bret have:

If we go for Fran's suggestion ...

// it's easy when nothing else is needed
json({}, {headers: HEADERS_CACHE_SHORT})

// it's weird when you need to add something else
json({}, {
  headers: {
    ...HEADERS_CACHE_SHORT,
    'some-header': 'value'
  }
})

whereas Bret's suggestion would be unambiguous

json({}, {
  headers: {
    'Cache-Control': HEADERS_CACHE_SHORT,
    'some-header': 'value'
  }
})

[frandiox]

How common is it to add extra headers, though? Wouldn't most of the times just be headers: HEADERS_CACHE_SHORT?
Plus, even in that situation I'd personally still prefer writing ... than 'Cache-Control' since for some reason I always misspell header names 😂

But just a random idea though, the current version is good as well 👍

[wizardlyhel]

mmm .. I like what Bret have:

If we go for Fran's suggestion ...

// it's easy when nothing else is needed
json({}, {headers: HEADERS_CACHE_SHORT})

// it's weird when you need to add something else
json({}, {
  headers: {
    ...HEADERS_CACHE_SHORT,
    'some-header': 'value'
  }
})

whereas Bret's suggestion would be unambiguous

json({}, {
  headers: {
    'Cache-Control': HEADERS_CACHE_SHORT,
    'some-header': 'value'
  }
})