| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
* chore: use monorepo
* chore: scaffold astro-scripts
* chore: move tests inside packages/astro
* chore: refactor tests, add scripts
* chore: move parser to own module
* chore: move runtime to packages/astro
* fix: move parser to own package
* test: fix prettier-plugin-astro tests
* fix: tests
* chore: update package-lock
* chore: add changesets
* fix: cleanup examples
* fix: starter example
* chore: update changeset config
* chore: update changeset config
* chore: setup changeset release workflow
* chore: bump lockfiles
* chore: prism => astro-prism
* fix: tsc --emitDeclarationOnly
* chore: final cleanup, switch to yarn
* chore: add lerna
* chore: update workflows to yarn
* chore: update workflows
* chore: remove lint workflow
* chore: add astro-dev script
* chore: add symlinked README
|
|
* fix(www): link styles (#100)
Co-authored-by: Nate Moore <nate@skypack.dev>
* Add `assets/` (#102)
* chore: add assets
* docs: update readme
Co-authored-by: Nate Moore <nate@skypack.dev>
* docs: fix readme
* docs: fix readme
* chore: remove github banner
* Allow multiple JSX in mustache
* Manually discard package-lock update (due to local use of npm v7)
* Tidy up
* Revert mode ts-ignore
Co-authored-by: Nate Moore <natemoo-re@users.noreply.github.com>
Co-authored-by: Nate Moore <nate@skypack.dev>
|
|
* Start of cli docs
* Document the CLI
Also adds support for the `--config` option and `--port` option for the dev server.
* Add tests for --config and --port flags
* Add port to validateConfig
|
|
* docs: fix readme
* chore: scaffold prettier plugin
* chore(prettier): switch to cjs
* test(prettier): scaffold prettier tests
* test(prettier): add simple prettier tests
* feat(prettier): first pass
* refactor: expose parser as CJS export
* test(prettier): add long expression
* refactor(prettier): use Astro parser + built-in prettier doc for prettier plugin
* chore: remove parser from git
* chore: add prettier-plugin-astro `build` to workflow
* chore: update package-lock
* chore: do not build prettier-plugin-astro
* fix: update engines
* chore: remove NPM restriction
* chore: fix workflow paths
* chore: update build script
* test: fix prettier expr test
* chore: fix parser build on windows
* refactor: add parser tsconfig, extending base config
* chore: relax ban-ts-comment
* chore: fix lint issue
Co-authored-by: Nate Moore <nate@skypack.dev>
|
|
|
|
Svelte component resolution wasn't handled correctly during the build.
Note that in the future we need to consolidate a "framework" API, so this stuff is not sprinkled throughout the codebase.
|
|
* Add Windows to test suite
* Try implicit URL
|
|
* add dep domhandler imported in in src/build/static
* lint and jsDoc error
* move domhandler to devDep
* chore: add package lock
* escape string jsDoc
* chore: add astro dep in until prism import is refactored
* chore: add snowpack example package lock
|
|
* Implement fallback capability
This makes it possible for a dynamic component to render fallback content on the server.
The mechanism is a special `static` prop passed to the component. If `static` is true then the component knows it can render static content.
Putting aside the word `static`, is this the right approach? I think giving components the flexibility to make the decision themselves *is* the right approach.
However in this case we have a special property that is passed in non-explicitly. I think we have to do it this way because if the caller passes in a prop it will get serialized and appear on the client. By making this something we *add* during rendering, it only happens on the server (and only when using `:load`).
Assuming this is the right approach, is `static` the right name for this prop? Other candidates:
* `server`
That's all I have!
* Use `import.meta.env.astro` to tell if running in SSR mode.
* Run formatter
|
Nate Moore
Kevin (Kun) "Kassimo" Qian
Matthew Phillips
matthewp
Drew Powers
duncanhealy
