BuilderIO / BuilderIO/nextjs-shopify

Next.js missing cache-control header may lead to CDN caching

Open
#52 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
485
Forks
246
PR merge metrics
No merged PRs in 30d

Description

PS C:\Users\gardi\OneDrive\Documents\GitHub\IEMweb\nextjs-shopify> npm audit fix

up to date, audited 859 packages in 3s

106 packages are looking for funding
run `npm fund` for details

# npm audit report

next 0.9.9 - 13.5.4-canary.11
Severity: moderate
Next.js missing cache-control header may lead to CDN caching empty reply - https://github.com/advisories/GHSA-c59h-r6p8-q9wc
Depends on vulnerable versions of postcss
fix available via `npm audit fix --force`
Will install next@13.5.6, which is outside the stated dependency range
node_modules/next

postcss <8.4.31
Severity: moderate
PostCSS line return parsing error - https://github.com/advisories/GHSA-7fh5-64p2-3v2j
fix available via `npm audit fix --force`
Will install next@13.5.6, which is outside the stated dependency range
node_modules/postcss

2 moderate severity vulnerabilities

To address all issues, run:
npm audit fix --force
PS C:\Users\gardi\OneDrive\Documents\GitHub\IEMweb\nextjs-shopify>

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the reported `npm audit` output in the project and inspect the dependency declarations for Next.js and PostCSS. Check the advised upgrade path for compatibility, then verify that the audit no longer reports these vulnerabilities and that the project still installs and builds successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
nextjs, typescript
Domain
devops, security
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.