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

Use dynamic import rather than require() for loading formatters #278

Merged
merged 2 commits into from
Jun 26, 2020

Conversation

kasperisager
Copy link
Contributor

These will still compile to CJS per our TypeScript configuration but will remove the dependency on Node.js and allow us to compile to native modules in the future. This change is breaking as it turns loading of formatters into an async operation.

@kasperisager kasperisager added the major Backwards-incompatible change that touches public API label Jun 25, 2020
@kasperisager kasperisager requested a review from Jym77 June 25, 2020 13:10
@kasperisager kasperisager self-assigned this Jun 25, 2020
@kasperisager kasperisager merged commit 63eec5a into master Jun 26, 2020
@kasperisager kasperisager deleted the async-formatter branch June 26, 2020 08:44
kasperisager added a commit that referenced this pull request Jul 1, 2020
* master: (21 commits)
  Rework the way DOM parent pointers are handled (#283)
  Create a GitHub release as part of release workflow
  Backtrack on shortcut links
  v0.3.0
  Prepare release
  Update changelog
  Update changelog
  `RoleOptions#allowPresentational` must be optional
  Update SIA R67 (#272)
  Update lockfile
  Correctly resolve important and overridden CSS properties (#282)
  Introduce HyperScript-like DSL for constructing DOM (#281)
  Use dynamic import rather than `require()` for loading formatters (#278)
  Add `Future#get()` and accept thunked promises in `Future.from()` (#279)
  Fix default argument type parameter of several types
  Speedup table building (#276)
  Add initial support for `background` shorthand property (#277)
  Output stack in CLI errors if available
  Chesterton's fence strikes again!
  Correctly pull `.message` from expectations
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
major Backwards-incompatible change that touches public API
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants