Age | Commit message (Collapse) | Author | Files | Lines |
|
Co-authored-by: Sarah Rainsberger <sarah@rainsberger.ca>
Co-authored-by: Princesseuh <princssdev@gmail.com>
Co-authored-by: Erika <3019731+Princesseuh@users.noreply.github.com>
|
|
|
|
Co-authored-by: Nate Moore <natemoo-re@users.noreply.github.com>
|
|
Co-authored-by: Nate Moore <natemoo-re@users.noreply.github.com>
|
|
|
|
|
|
|
|
* override wrong positions in browser history
* Lost events are taken into account during throttling
|
|
* Fix #7056 Splashing Navigation Menu in portfolio template
* Add menu back to no-JS view
* Fix desktop view in non-JS & menu styling
* chore: force ci
---------
Co-authored-by: Nate Moore <nate@astro.build>
Co-authored-by: Nate Moore <natemoo-re@users.noreply.github.com>
|
|
|
|
* feat(create-astro): verify that --template exists
* feat: verify internet connectivity
* chore: skip connectivity check on --dry-run
* chore: fix lint
|
|
* chore: fix flaky CF test
* chore: increase wrangler timeout
|
|
astro:server:setup hook (#8104)
* All astro integrations hooks are defined as returning void|Promise, so
all calls need to deal with a possible async/await pattern. One was
missed in vite-plugin-integrations-container.
This plugin is definitely used by the astro-dev when using a node
adapter, but I am not sure about other such scenarios. I did a search
through the code base, and all other runHook* calls are properly
awaited.
* chore: make test async
---------
Co-authored-by: Nate Moore <nate@astro.build>
|
|
Co-authored-by: Elian ☕️ <hello@elian.codes>
Co-authored-by: Nate Moore <natemoo-re@users.noreply.github.com>
|
|
|
|
* wip: support true react vnodes in renderer
* Add new experimentalReactChildren option to React integration
* Update the test
* Add docs
* Update packages/integrations/react/server.js
Co-authored-by: Nate Moore <natemoo-re@users.noreply.github.com>
* Update with a better test
* Update .changeset/yellow-snakes-jam.md
Co-authored-by: Sarah Rainsberger <sarah@rainsberger.ca>
* Update packages/integrations/react/README.md
Co-authored-by: Sarah Rainsberger <sarah@rainsberger.ca>
* Update packages/integrations/react/README.md
Co-authored-by: Sarah Rainsberger <sarah@rainsberger.ca>
---------
Co-authored-by: Nate Moore <nate@astro.build>
Co-authored-by: Nate Moore <natemoo-re@users.noreply.github.com>
Co-authored-by: Sarah Rainsberger <sarah@rainsberger.ca>
|
|
* refactor: build pipeline
* refactor: build pipeline
* fix: manifest not extensible and correct directory for renderers.mjs
* fix: correctly resolve output directory
* fix: correctly compute encoding and body
* chore: update documentation
* refactor: change how tests are run
* refactor: fix test regressions!!
|
|
|
|
* fix(#7933, plt-789): cleanup dotfiles during build
* chore: add changeset
|
|
|
|
Co-authored-by: Sarah Rainsberger <sarah@rainsberger.ca>
Co-authored-by: Emanuele Stoppa <my.burning@gmail.com>
|
|
* Filter out Svelte's unexpected class prop console warnings
Astro's hydration code passes a `class` prop to Svelte components, inducing Svelte to log a warning about an unknown prop. Preempting this by exporting a `class` prop from the Svelte component isn't a viable workaround since `class` is a reserved identifier in JS.
This PR implements the console-filtering workaround suggested by @HiDeoo in #5665, borrowing the `useConsoleFilter` approach from the [preact integration](https://github.com/withastro/astro/blob/a1c0cbe604c9f91cdc421b5606aab574999eba01/packages/integrations/preact/src/server.ts#L72-L94).
It would probably be better to generalize console filtering so it could be shared across multiple integrations.
Ideally there would be a way to handle this in Svelte, but as was pointed out in the issue thread even they resort to [similar cringe-inducing hackery](https://github.com/sveltejs/kit/blob/master/packages/kit/src/runtime/client/client.js#L1974-L1996) in sveltekit.
* Only filter Svelte console warnings in dev builds
* Add changeset
* Fix lint error.
---------
Co-authored-by: bluwy <bjornlu.dev@gmail.com>
Co-authored-by: Nate Moore <natemoo-re@users.noreply.github.com>
|
|
|
|
|
|
* [ci] release
* Update packages/create-astro/CHANGELOG.md
---------
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: Nate Moore <natemoo-re@users.noreply.github.com>
|
|
|
|
|
|
|
|
Co-authored-by: Darius <19603573+itsMapleLeaf@users.noreply.github.com>
|
|
|
|
* chore: update wrangler
* chore(cloudflare): update tests to support wrangler@3
* chore(cloudflare): update debug message
* chore: force ci
|
|
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
|
|
(#8035)
|
|
Co-authored-by: Matthew Phillips <matthew@matthewphillips.info>
|
|
|
|
Co-authored-by: Sarah Rainsberger <sarah@rainsberger.ca>
|
|
|
|
|
|
|
|
|
|
|
|
* fix astro assets support in cloudflare
* add changeset
|
|
|
|
|
|
This was causing React components rendered with client:only
to be prefixed with null. While not technically causing any
issues, it is unintended and could be considered a bug.
Co-authored-by: Nate Moore <natemoo-re@users.noreply.github.com>
|
|
|
|
* astro add cli pass down arguments to install cmd
* add changeset
* feat: pass common flags down to install command
* Update .changeset/soft-colts-heal.md
---------
Co-authored-by: Elod Tobak <tobakelod@gmail.com>
|
|
* Update types to specify that compress defaults to true
* Update astro.ts
---------
Co-authored-by: Sarah Rainsberger <sarah@rainsberger.ca>
|
|
|
|
Co-authored-by: Erika <3019731+Princesseuh@users.noreply.github.com>
Co-authored-by: Princesseuh <princssdev@gmail.com>
|