DylanPiercey
Repos
156
Followers
230
Following
414

🗺 Universal router for web applications.

570
9

A declarative, HTML-based language that makes building web apps fun

12105
586

A module to create readable `"multipart/form-data"` streams. Can be used to submit forms and file uploads to other web applications.

2131
257

Find out minified and gzipped npm package size

179
4

📑 Lightweight dom diffing with plain old html.

178
16

Events

chore: add todo

fix: ts-plugin resolve modules bug

wip: bring in typescript extractor code

fix: add language-tools as a dep of language-server

feat: integrate new language-tools package and move css extractor there

chore: rename stylesheet service folder

fix: extractor not including end of range offsets

refactor: avoid using unique symbol

Created at 5 hours ago
issue comment
Support "worker" export condition when ssr.target is "webworker"

@manucorporat I think you could still differentiate by using nested export conditions like so:

"exports": {
  "browser": {
      "worker": "target browsers web workers",
      "default": "regular browser import"
   },
   "node": {
      "worker": "worker in a node environment",
      "default": "regular node script"
    },
    "worker": "probably edge?",
    "default": "🤷‍♂️"
}
Created at 1 day ago
delete branch
DylanPiercey delete branch changeset-release/main
Created at 3 days ago

[ci] release (#147)

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

Created at 3 days ago
pull request closed
[ci] release

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

htmljs-parser@5.2.2

Patch Changes

  • #146 bcfd809 Thanks @DylanPiercey! - Fixes an issue where attribute names that started with a keyword (eg: as-thing or instanceof-thing) were incorrectly treated as an expression continuation.
Created at 3 days ago
delete branch
DylanPiercey delete branch fix-issue-parsing-attr-names-starting-with-keyword
Created at 3 days ago

fix: ensure keyword operators are always followed by a space (#146)

Created at 3 days ago
pull request closed
fix: ensure keyword operators are always followed by a space

Fixes an issue where attribute names that started with a keyword (eg: as-thing or instanceof-thing) were incorrectly treated as an expression continuation.

Created at 3 days ago
pull request opened
fix: ensure keyword operators are always followed by a space

Fixes an issue where attribute names that started with a keyword (eg: as-thing or instanceof-thing) were incorrectly treated as an expression continuation.

Created at 3 days ago
create branch
DylanPiercey create branch fix-issue-parsing-attr-names-starting-with-keyword
Created at 3 days ago
delete branch
DylanPiercey delete branch changeset-release/main
Created at 1 week ago

[ci] release (#1881)

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

Created at 1 week ago
pull request closed
[ci] release

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@marko/compiler@5.23.2

Patch Changes

  • #1880 c4cce33e8 Thanks @DylanPiercey! - Fix an issue where merging scripts (via the out.script api) was not properly inserting delimeters when scripts are added in different async writers.

marko@5.22.2

Patch Changes

  • #1880 c4cce33e8 Thanks @DylanPiercey! - Fix an issue where merging scripts (via the out.script api) was not properly inserting delimeters when scripts are added in different async writers.

  • Updated dependencies [c4cce33e8]:

    • @marko/compiler@5.23.2
    • @marko/translator-default@5.22.2

@marko/translator-default@5.22.2

Patch Changes

  • #1880 c4cce33e8 Thanks @DylanPiercey! - Fix an issue where merging scripts (via the out.script api) was not properly inserting delimeters when scripts are added in different async writers.
Created at 1 week ago
delete branch
DylanPiercey delete branch fix-script-merging-delimeter
Created at 1 week ago

fix: ensure delimeter added when scripts merged across async writers (#1880)

Created at 1 week ago
pull request closed
fix: ensure delimiter added when scripts merged across async writers

Description

Fix an issue where merging scripts (via the out.script api) was not properly inserting delimiters when scripts are added in different async writers.

Specifically these scripts should be joined by ;.

Checklist:

  • [x] I have read the CONTRIBUTING document and have signed (or will sign) the CLA.
  • [ ] I have updated/added documentation affected by my changes.
  • [x] I have added tests to cover my changes.
Created at 1 week ago
pull request opened
fix: ensure delimiter added when scripts merged across async writers

Description

Fix an issue where merging scripts (via the out.script api) was not properly inserting delimiters when scripts are added in different async writers.

Specifically these scripts should be joined by ;.

Checklist:

  • [x] I have read the CONTRIBUTING document and have signed (or will sign) the CLA.
  • [ ] I have updated/added documentation affected by my changes.
  • [x] I have added tests to cover my changes.
Created at 1 week ago
create branch
DylanPiercey create branch fix-script-merging-delimeter
Created at 1 week ago
pull request closed
fix: update state when calling mutate

Calling mutate for gql-mutation is not updating state for fetching and response from mutate.

Description

Apply state to a component as a setter is not affecting component state because component.state is not an instance of State. So to update a state from template we need to call component.setState.

Checklist:

  • [ ] I have updated/added documentation affected by my changes.
  • [x] I have added tests to cover my changes.
Created at 1 week ago

fix: update state when calling mutate (#9)

Created at 1 week ago
issue comment
fix: update state when calling mutate

@FiodorGherasimenco it looks good and CI is passing. Could you sign the CLA?

Created at 1 week ago
issue comment
fix: update state when calling mutate

Good catch, thanks for the PR!

Created at 1 week ago
delete branch
DylanPiercey delete branch allow-dev-ssl-certs
Created at 2 weeks ago

fix: honor NODE_TLS_REJECT_UNAUTHORIZED env var

Created at 2 weeks ago
pull request closed
fix: honor NODE_TLS_REJECT_UNAUTHORIZED env var

Description

Forwards the NODE_TLS_REJECT_UNAUTHORIZED environment variable to the default SSR fetch implementation (allows working with dev mode self signed ssl certs).

Created at 2 weeks ago
pull request opened
fix: honor NODE_TLS_REJECT_UNAUTHORIZED env var

Description

Forwards the NODE_TLS_REJECT_UNAUTHORIZED environment variable to the default SSR fetch implementation (allows working with dev mode self signed ssl certs).

Created at 2 weeks ago
create branch
DylanPiercey create branch allow-dev-ssl-certs
Created at 2 weeks ago
delete branch
DylanPiercey delete branch fixes-01-12-23
Created at 2 weeks ago
pull request closed
Consistency improvements and refactoring

Description

  • Supports a relative url for the default fetch implementation in SSR mode (means you should be able to use a relative url for the gql-client and it'll be resolved relative to the current request).
  • Placeholders are now rendered inside a wrapper div on both the server and the browser (previously only the browser renderer had the wrapper).
  • error is now properly serialized and passed in for both ssr and csr modes.

Other refactoring and cleaning.

Created at 2 weeks ago

fix: improve placeholder rendering and error handling

feat: support relative url for default ssr fetch implementation

Created at 2 weeks ago