feat: Add NextJS example

[kbieganowski]

Summary

Added NextJS example based on Vite tests in examples/web-vite (#226)

[changeset-bot]

⚠️ No Changeset found

Latest commit: eb88c15

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[thymikee]

Lovely!

[Xiltyn]

I believe we still need some things to be complete here @thymikee. I'm working with @kbieganowski on this one ;)

[Xiltyn]

Unfortunately, at the moment we're experiencing issues with building the Next example using Bob. Based on the information provided by @kbieganowski, the issues appears to lie in Next custom tags used for things like styling. This is related to how Bob handles babel and the fact, that Next.js currently doesn't play well with this setup.

That being said, because this will always only be a problem in our repo, I recommended to adjust the example so that it doesn't use those custom tags. When a Next.js user downloads reassure package, they will not have this issue, because they will not have to build our internal Next.js example, they would have gotten a built library.

We should at the same time mention this in our documentation so that w don't focus potential users who want to play around. We could also provide a hint on hacking the setup in order to make it work if we know how to do it.

cc: @thymikee @mdjastrzebski

[mdjastrzebski]

Pls update this README file to explain that this is plain NextJS app straight from the CLI tool with Reassure atteched. And how to run the reassure tests.

[mdjastrzebski]

Pls use yarn to install packages, as all other examples use it.

[mdjastrzebski]

It seems that both yarn.lock and package-lock.json (NPM) are present. Pls remove NPM's one.

[mdjastrzebski]

Removed

[mdjastrzebski]

Do not add nextjs here. All examples except from examples/native are not using monorepo, as this causes version conflicts for react versions/etc

Suggested change

"examples/web-nextjs"

[mdjastrzebski]

Removed

[Xiltyn]

@kbieganowski
Please update the ESLint setup so that we don't collide with react-native specific rules, e.g. no strings within tags.

cc: @mdjastrzebski

[Xiltyn]

Great job! There are still some small bits to iron out. It looks like the issues with custom tags have been dealt with as far as I can see, nice!

We still need to update ESLint rules and align code styling to match our prettier config.

[mdjastrzebski]

Looks good! Awesome work @kbieganowski and @Xiltyn.

Let's fix the lint, I think we can simply disable linting in examples/web-nextjs.

Also let's update examples Readme file, to describe our example rather than NextJS default

[Xiltyn]

I believe we're good here, there is a small ReadMe file update, but it's a minor thing I will ammend before merge if necessary.