-
Notifications
You must be signed in to change notification settings - Fork 673
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Pages Functions example test project #617
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome! More examples 😄
c7111d8
to
8b51dec
Compare
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/1994105676/npm-package-wrangler-617 You can reference the automatically updated head of this PR with: npm install --save-dev https://prerelease-registry.developers.workers.dev/prs/617/npm-package-wrangler-617 Or you can use npx https://prerelease-registry.developers.workers.dev/runs/1994105676/npm-package-wrangler-617 dev path/to/script.js |
This is breaking tests when running locally because of the open ports :( Could y'all fix this soonish? |
#620 :) |
🦋 Changeset detectedLatest commit: 8b51dec The changes in this PR will be included in the next version bump. 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 |
Looks like we forgot to run `npm install` at the root in #617. Also removed an unnecessary `typescript` dependency.
Looks like we forgot to run `npm install` at the root in #617. Also removed an unnecessary `typescript` dependency.
Previously, if source maps included relative paths, those paths would not be resolved relative to the source map's own file path before inclusion into stack traces. This meant stack traces included relative paths that couldn't be resolved for click-to-definition by IDEs. This change includes the URL of the source map upon retrieval, allowing `source-map-support` to include absolute source URLs in stack traces.
Previously, if source maps included relative paths, those paths would not be resolved relative to the source map's own file path before inclusion into stack traces. This meant stack traces included relative paths that couldn't be resolved for click-to-definition by IDEs. This change includes the URL of the source map upon retrieval, allowing `source-map-support` to include absolute source URLs in stack traces.
Previously, if source maps included relative paths, those paths would not be resolved relative to the source map's own file path before inclusion into stack traces. This meant stack traces included relative paths that couldn't be resolved for click-to-definition by IDEs. This change includes the URL of the source map upon retrieval, allowing `source-map-support` to include absolute source URLs in stack traces.
Previously, if source maps included relative paths, those paths would not be resolved relative to the source map's own file path before inclusion into stack traces. This meant stack traces included relative paths that couldn't be resolved for click-to-definition by IDEs. This change includes the URL of the source map upon retrieval, allowing `source-map-support` to include absolute source URLs in stack traces.
A simple Functions test project which confirms that: