Bug fix: Don't use acorn just because file ends with comment - #17
Merged
Conversation
Macil
changed the title
Macil
changed the title
goto-bus-stop
approved these changes
Dec 25, 2017
7 tasks
00o-sh
added a commit
to unabandoned/syntax-error
that referenced
this pull request
Aug 14, 2026
## What & why Adds `.unabandoned.yml` at the repo root for **@unabandoned/syntax-error** — the hand-authored editorial metadata (upstream source + why it's abandoned, a one-line summary, why we carry the fork, and its `@unabandoned/*` consumers) that the central dashboard reads straight from this fork's default branch. Only editorial facts the GitHub API can't derive are recorded; everything derivable (open PRs/issues, releases, CI, pending Renovate updates) is deliberately left out so it can't go stale. Schema-validated against `unabandoned/.github`'s `scripts/validate_metadata.py` (prints `ok`); once PR browserify#17 lands, `reusable-ci` validates it automatically on every fork PR. ## Type of change - [ ] `fix` / `feat` / `perf` — consumer-facing - [ ] `deps` — dependency update (add the `security` label if it fixes a CVE) - [x] `chore` / `ci` / `build` / `docs` / `test` / `refactor` — maintenance ## Checklist - [x] Commits follow Conventional Commits (`commitlint` passes) - [x] `npm test` passes on Node 20 / 22 / 24 — metadata-only change; no JS or test surface touched - [x] No new runtime dependency (or its addition is justified below) - [x] Dev tree kept lean (prefer built-in `node:test` over new runners) --- _Generated by [Claude Code](https://claude.ai/code/session_01E3Yvr9snA7KG1jCToqKKvp)_
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
If a file ends with a single-line comment, then in the quick-eval test, the "})()" appended to the end is commented out, the file unnecessarily fails the quick-eval test, and then the file is parsed with acorn.
When using browserify with sourcemaps enabled, it appears that every source string processed here ends with a single-line comment containing the sourcemap, so everything gets parsed by acorn here. I noticed this while using a profiler on a project's build.
This pull requests makes it so "\n})()" is appended to the end, preventing files ending in single-line comments from triggering an acorn parse.