Skip to content
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

update origin master #10

Merged
merged 123 commits into from
Jun 25, 2024
Merged

Conversation

lheberlie
Copy link
Collaborator

@lheberlie lheberlie commented Jun 25, 2024

upstream->master
update-origin-master-from-origin-upstream
origin->master

hegemonic and others added 30 commits December 5, 2023 16:01
Because we now share `env` by passing it around, not by relying on the module cache.
It turns out that JSDoc's dependency-injection needs are pretty simple; we mostly just need to pass around some data, plus some logging functions. That means the previous solution was overengineered, even though it was still pretty lightweight.

Now we just put everything in the `Env` object and pass that around instead.
I did some quick-and-dirty profiling, and these functions made up ~2% of the flamegraph, mostly for when they called through to the type parser; also, it's likely that they'll be called repeatedly with many of the same inputs. Memoizing the functions cuts them to ~1% of the flamegraph.
 - jsdoc@5.0.0-dev.16
 - @jsdoc/ast@0.2.10
 - @jsdoc/cli@0.3.9
 - @jsdoc/core@0.5.7
 - @jsdoc/doclet@0.2.10
 - @jsdoc/eslint-config@1.2.8
 - @jsdoc/parse@0.3.10
 - @jsdoc/plugins@0.1.10
 - @jsdoc/prettier-config@0.2.7
 - @jsdoc/tag@0.2.10
 - @jsdoc/task-runner@0.2.4
 - @jsdoc/template-legacy@0.1.10
Starting point for a public API for JSDoc.
hegemonic and others added 28 commits May 11, 2024 17:42
Previously, we used `exports.NAME`, which was both incorrect and confusing.
@lheberlie lheberlie merged commit d04e338 into master Jun 25, 2024
8 checks passed
@lheberlie lheberlie deleted the update-origin-master-from-origin-upstream branch June 25, 2024 18:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants