No description
Find a file
Rodrigo Esteves 9e5116975d
Upgrading react-ga to react-ga4 (#48932)
taken from google analytic's page:

 "_On July 1, 2023, this property will stop processing data. Starting in March 2023, for continued website measurement, migrate your original property settings to a Google Analytics 4 (GA4) property, or they'll be copied for you to an existing GA4 property, reusing existing site tags._"

The package 'react-ga' doesn't support GA4, so i updated the package to 'react-ga4', the example continues primarily the same, the only differences is that specifying 'pageview' is now required instead of just setting the location of the pageview and the expection() function doesn't exist in this package.

required changes are welcomed




Co-authored-by: Steven <229881+styfle@users.noreply.github.com>
2023-05-16 22:06:09 +00:00
.cargo build(cargo): move workspaces manifest to top level (#48198) 2023-04-19 18:38:36 +02:00
.config build(cargo): move workspaces manifest to top level (#48198) 2023-04-19 18:38:36 +02:00
.devcontainer re-enable next-dev-tests (#47087) 2023-03-14 16:05:19 +01:00
.github fix: Disable tracing/release_max_level_off for wasm, too (#49639) 2023-05-15 16:16:12 +02:00
.husky Replace pre-commit with husky (#38350) 2022-07-06 11:14:16 -05:00
.vscode Optimize trace span relationships (#49697) 2023-05-12 13:01:07 +02:00
bench Replace var with const (#49379) 2023-05-09 10:25:39 +02:00
contributing update example Deploy button URLs (#48842) 2023-04-26 13:31:44 -04:00
docs Add --use-yarn flag to create-next-app (#49407) 2023-05-10 14:51:12 +02:00
errors [docs] Add iOS hydration mismatch details to error page (#43584) 2023-05-09 12:55:41 +02:00
examples Upgrading react-ga to react-ga4 (#48932) 2023-05-16 22:06:09 +00:00
packages refactor(next-core): move transforms to plugin (#49621) 2023-05-16 17:47:31 +00:00
scripts refactor(scripts): fix clippy errors (#49719) 2023-05-12 19:14:30 +00:00
test Fix conflict when re-exporting multiple Client References (#49468) 2023-05-16 12:35:12 +02:00
.alexignore Integrate next-* crates from Turbopack (#47019) 2023-03-13 14:33:17 +01:00
.alexrc docs: Add "special" to the Alex allowlist (#48021) 2023-04-06 16:32:06 +02:00
.eslintignore chore: Add .vscode to eslintignore (#48020) 2023-04-07 15:51:26 +00:00
.eslintrc.json Update MetadataRoute to namespace (#47674) 2023-03-30 15:27:44 -07:00
.gitattributes the way towards webpack 5 typings (#29105) 2021-09-21 19:17:16 +02:00
.gitignore Remove unused code from test-pack turbo task (#48487) 2023-04-18 12:12:00 +00:00
.npmrc fix: npm publish provenance permissions (#48757) 2023-04-24 14:08:55 +00:00
.prettierignore add test cases for error handling (#49093) 2023-05-02 22:09:55 +02:00
.prettierignore_staged hmr error improvements (#30616) 2023-01-06 20:35:16 +01:00
.prettierrc.json Prettier trailingComma default value to es5 since 2.0 (#14391) 2020-06-22 13:25:24 +02:00
.rustfmt.toml build(cargo): move workspaces manifest to top level (#48198) 2023-04-19 18:38:36 +02:00
azure-pipelines.yml Update min Node.js version to v16 (#48903) 2023-04-27 07:31:27 +00:00
Cargo.lock chore(turbopack): Update swc_core to v0.76.6 (#49792) 2023-05-16 05:08:17 +00:00
Cargo.toml chore(turbopack): Update swc_core to v0.76.6 (#49792) 2023-05-16 05:08:17 +00:00
CODE_OF_CONDUCT.md updated code of conduct to v2.1 (#34208) 2022-02-10 18:11:42 -06:00
contributing.md chore: improve repo templates (#46629) 2023-03-01 09:25:51 -08:00
jest.config.js Refactor and add more tests to next/font/local (#46627) 2023-03-01 15:31:45 -08:00
jest.replay.config.js Add Replay integration for dev e2e tests (#40955) 2022-09-29 14:45:10 -07:00
lerna.json v13.4.3-canary.1 2023-05-16 03:01:47 +00:00
license.md Update license year (#44403) 2023-01-01 11:12:49 +01:00
lint-staged.config.js Run dev tests against default CNA templates (#45211) 2023-01-24 11:01:03 -08:00
package.json chore: cross-platform rm -rf script (#49529) 2023-05-10 01:14:37 +00:00
plopfile.js Opt-in to dynamic rendering when reading searchParams (#46205) 2023-03-16 21:46:35 +01:00
pnpm-lock.yaml chore(turbopack): Update swc_core to v0.76.6 (#49792) 2023-05-16 05:08:17 +00:00
pnpm-workspace.yaml Integrate next-* crates from Turbopack (#47019) 2023-03-13 14:33:17 +01:00
readme.md Monorepo (#5341) 2018-10-01 01:02:10 +02:00
release.js Fix labels for release sections 2021-11-21 13:11:54 +01:00
run-tests.js ci(test): enable turbopack test (#49466) 2023-05-09 10:46:54 -07:00
rust-toolchain build(cargo): move workspaces manifest to top level (#48198) 2023-04-19 18:38:36 +02:00
test-file.txt Add additional file serving tests (#12479) 2020-05-04 11:58:19 -05:00
tsconfig-tsec.json Integrate tsec into the linting process (#33746) 2022-02-24 16:59:18 -08:00
tsconfig.json Integrate next-* crates from Turbopack (#47019) 2023-03-13 14:33:17 +01:00
tsec-exemptions.json Move core files to src folder and move JS files to TypeScript (#44405) 2023-01-03 10:05:50 +01:00
turbo.json feat: Allow trace-level logging for non-published release builds (#49564) 2023-05-10 14:50:36 +02:00
UPGRADING.md Move upgrading guide to /docs (#10727) 2020-02-28 23:46:18 +01:00
vercel.json Silence GH Comments for Preview URLs (#18766) 2020-11-03 21:59:47 +00:00

Next.js

Getting Started

Visit https://nextjs.org/learn to get started with Next.js.

Documentation

Visit https://nextjs.org/docs to view the full documentation.

Who is using Next.js?

Next.js is used by the world's leading companies. Check out the Next.js Showcase to learn more.

Community

The Next.js community can be found on GitHub Discussions, where you can ask questions, voice ideas, and share your projects.

To chat with other community members you can join the Next.js Discord.

Our Code of Conduct applies to all Next.js community channels.

Contributing

Please see our contributing.md.

Good First Issues

We have a list of good first issues that contain bugs that have a relatively limited scope. This is a great place to get started, gain experience, and get familiar with our contribution process.

Authors

Security

If you believe you have found a security vulnerability in Next.js, we encourage you to responsibly disclose this and not open a public issue. We will investigate all legitimate reports. Email security@vercel.com to disclose any security vulnerabilities.

https://vercel.com/security