fix: site.entry-point should not be a hard deprecation

[threepointone]

To make migration of v1 projects easier, Sites projects should still work, including the entry-point field (which currently errors out). This enables site.entry-point as a valid entry point, with a deprecation warning.

---

I also added an example repo, which is simply the output of wrangler generate --site

[changeset-bot]

🦋 Changeset detected

Latest commit: 7d81a81

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
wrangler	Patch

Not sure what this means? Click here to learn what changesets are.

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

[github-actions]

A wrangler prerelease is available for testing. You can install this latest build in your project with:

npm install --save-dev https://prerelease-registry.developers.workers.dev/runs/2266650886/npm-package-wrangler-843

You can reference the automatically updated head of this PR with:

npm install --save-dev https://prerelease-registry.developers.workers.dev/prs/843/npm-package-wrangler-843

Or you can use npx with this latest build directly:

npx https://prerelease-registry.developers.workers.dev/runs/2266650886/npm-package-wrangler-843 dev path/to/script.js

[caass]

This looks pretty good.

The example app is just copied directly from wrangler 1, right?

The messaging is a little confusing to me. The deprecation warning is that site.entry-point is no longer used, but actually it seems like we do actually respect it? If that's the case, then maybe we should instead encourage people to move site.entry-point to main?

Like basically my nit is that the messaging implies we're ignoring site.entry-point but actually...we're not. I think..? Other than that though, looks good :)

[threepointone]

Good point about the messages, I reused what it already was. I'll rewrite it.

[threepointone]

tbh I did such a shoddy job with this PR, noticing that I just commented out a couple of tests I should have implemented. Working today on making this a lot better.

[threepointone]

Alright, let's try this again. Messaging better aligned with our other deprecations, better tests. What do you think?

[caass]

Nice! Approving with some minor nits that you can do if you want, and a request to create a follow-up issue for normalizing windows paths in tests

[threepointone]

Thanks for the reviews and the patience peeps. Landing this now.