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

npm spec eats translation errors #112

Closed
mikesamuel opened this issue Jan 16, 2019 · 0 comments
Closed

npm spec eats translation errors #112

mikesamuel opened this issue Jan 16, 2019 · 0 comments

Comments

@mikesamuel
Copy link
Collaborator

gulp spec and gulp spec.watch use npmjs.com/package/bikeshed-js which is nice since it falls back to the bikeshed webservice if you haven't installed bikeshed locally, but which eats errors.

Right now, gulp spec

  • dumps error output to the HTML target file instead of the console
  • silently eats non-zero response codes
  • it's not obvious how to specify strict flags.

I ran

$ bikeshed --die-on link-error --print console spec spec/index.bs dist/spec/index.html

during local development .

Maybe rewrite the gulp file to just call out to bikeshed when it's available on PATH.

The bikeshed executable has a watch command so setting up the watcher to be equivalent shouldn't be super hard.

koto added a commit to koto/trusted-types that referenced this issue Mar 12, 2021
Spec is now built only via locally-installed Bikeshed (https://tabatkins.github.io/bikeshed/).

Fixes w3c#112, but now Bikeshed must be installed. Removed 'spec' target
from the pre-commit hooks.
@koto koto closed this as completed in 679456b Mar 12, 2021
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

No branches or pull requests

1 participant