66597be8a7
### Reason for making this change https://yarnpkg.com/getting-started/qa#:~:text=yarn%2Finstall%2Dstate.,your%20workspaces%20all%20over%20again. In the official documentation of `yarn`, it is stated that `.yarn/install-state.gz` is an optimization file that developer shouldn't ever have to commit. However, currently, when running `create-next-app`, `.yarn/install-state.gz` is being commited. ### Remaining work I apologize for only modifying one template initially to initiate the discussion first. If this change is agreed upon, it should be synchronized with other `.gitignore` templates. Would it be possible to follow a similar approach as in https://github.com/vercel/next.js/pull/47241? I would appreciate any assistance in syncing this change. |
||
---|---|---|
.. | ||
_pages | ||
app | ||
lib | ||
public | ||
.env.local.example | ||
.gitignore | ||
package.json | ||
README.md |
Example app using Facebook Pixel
This example shows how to use Next.js along with Facebook Pixel. A custom _document is used to inject base code. A _app is used to track route changes and send page views to Facebook Pixel.
Deploy your own
Deploy the example using Vercel:
How to use
Execute create-next-app
with npm, Yarn, or pnpm to bootstrap the example:
npx create-next-app --example with-facebook-pixel with-facebook-pixel-app
yarn create next-app --example with-facebook-pixel with-facebook-pixel-app
pnpm create next-app --example with-facebook-pixel with-facebook-pixel-app
Next, copy the .env.local.example
file in this directory to .env.local
(which will be ignored by Git):
cp .env.local.example .env.local
Set the NEXT_PUBLIC_FACEBOOK_PIXEL_ID
variable in .env.local
to match your facebook app's pixel ID.
Deploy it to the cloud with Vercel (Documentation).