[go: nahoru, domu]

[l10n] Replace fs.writeFileSync with writeIfChanged

We want to use the functions from `collect-strings.js` and
`bake-ctc-to-lhl.js` as a build step in the upcoming CL. This means
we should write the output files only if they are changed, otherwise
we'll confuse ninja and rebuild things unnecessarily. (Ninja is
timestamp based).

This CL replaces the unconditinal write with the `writeIfChanged`
helper we use everywhere else in node scripts used during build time.

R=kimanh@chromium.org

Bug: 1185727
Change-Id: I8ebb41a2492b03292198dc4d00947792ccd5594c
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4042207
Reviewed-by: Kim-Anh Tran <kimanh@chromium.org>
Commit-Queue: Simon Zünd <szuend@chromium.org>
2 files changed
tree: 6b889f59ea5b5bae79620f2026ab26b4c2c82279
  1. .vscode/
  2. build_overrides/
  3. config/
  4. docs/
  5. extension-api/
  6. front_end/
  7. inspector_overlay/
  8. node_modules/
  9. scripts/
  10. test/
  11. third_party/
  12. v8/
  13. .clang-format
  14. .editorconfig
  15. .eslintignore
  16. .eslintrc.js
  17. .gitattributes
  18. .gitignore
  19. .gn
  20. .mailmap
  21. .npmignore
  22. .npmrc
  23. .style.yapf
  24. .stylelintignore
  25. .stylelintrc.json
  26. AUTHORS
  27. BUILD.gn
  28. codereview.settings
  29. DEPS
  30. LICENSE
  31. OWNERS
  32. package-lock.json
  33. package.json
  34. PRESUBMIT.py
  35. README.md
  36. tsconfig.json
  37. WATCHLISTS
README.md

Chrome DevTools frontend

npm package

The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.

Source code

The frontend is available on chromium.googlesource.com.

Project documentation

Check out the project documentation for instructions to set up, use, and maintain a DevTools front-end checkout, as well as design guidelines, and architectural documentation.

Additional references

Source mirrors

DevTools frontend repository is mirrored on GitHub.

DevTools frontend is also available on NPM as the chrome-devtools-frontend package. It's not currently available via CJS or ES modules, so consuming this package in other tools may require some effort.

The version number of the npm package (e.g. 1.0.373466) refers to the Chromium commit position of latest frontend git commit. It's incremented with every Chromium commit, however the package is updated roughly daily.

Getting in touch