fix: Errors and remove unused code of docs and blog#2014
fix: Errors and remove unused code of docs and blog#2014PatrykKuniczak wants to merge 11 commits intowxt-dev:mainfrom
Conversation
✅ Deploy Preview for creative-fairy-df92c4 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
@aklinker1 I want to configure Second approach could be to use plugin for prettier, but stylelint works like eslint + prettier for CSS and IMHO it could be better for that case. |
c818537 to
279000b
Compare
@wxt-dev/analytics
@wxt-dev/auto-icons
@wxt-dev/browser
@wxt-dev/i18n
@wxt-dev/module-react
@wxt-dev/module-solid
@wxt-dev/module-svelte
@wxt-dev/module-vue
@wxt-dev/runner
@wxt-dev/storage
@wxt-dev/unocss
@wxt-dev/webextension-polyfill
wxt
commit: |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2014 +/- ##
==========================================
+ Coverage 76.11% 76.18% +0.06%
==========================================
Files 113 113
Lines 3027 3027
Branches 679 679
==========================================
+ Hits 2304 2306 +2
+ Misses 640 638 -2
Partials 83 83 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@aklinker1 Also take a look on that one |
6e744ef to
5fcdb6f
Compare
|
@aklinker1 You've already answered about |
…nd fix vitepress vite version conflict
…readability of each extension statistics
…ar and simplify custom.css overall
…error to groupIconVitePlugin
3fed7f3 to
4ae51b1
Compare
Overview
@ts-expect-error, for permanent solution, we need to wait till vitepress v2.0 will be released, that's bizzare, all of those changes are in alpha stage for a year):rootand use it inside@mediabut it isn't possible in native CSS and possible solutions isn't good enough, and i need to give up with this idea, only good solution IMHO is to use Tailwindcss to achive this in good quality :)Manual Testing
Let's check if blog works well :)