This pushes bottom transition to a background level while setting it so
that any z-indexes are isolated within the hero to avoid any other
weirdness from happenning.
It seems that Nuxt Turnstile's way of setting the key in `runtimeConfig`
is broken and doesn't work properly, resulting in an error in runtime,
because it has to be set. This commit sets the key in `runtimeConfig`
manually instead, which seems to fix the issue.
It seems that Rollup node-resolve module doesn't properly deal with
trailing slashes, causing it to thing that `string_decoder` is a
built-in Node.js dependency and attempt to import it from `unenv`, which
will obviously fail, because `string_decoder` is not, in fact, a Node.js
dependency, but an individual dependency of `readable-stream`.
This adds a small patch for `readable-stream@2.3.8` dependency, which
removes the leading slash, which seems to fix the builds.
This probably should be reported to relevant developers (Rollup
node-resolve plugin or Nitro?).
* Update Nuxt dependencies
* Fix ref access in ChartDisplay
* Fix feature flags cookie options type error
* Specify type-only imports
* Fix shorthands access to tags outside of reactive scope
* Replace most useRoute calls with useRoute from vue-router
Nuxt's version of this composable is horrendously broken (nuxt/nuxt#21340)
* Import all svgs with ?component parameter
Fixes weird hydration issues + gives correct type
* Add new links card and feature flag system for incremental dev.
* Switch to env variable for dev flags
* Add members card
* fix order of creators card
* Fix owner icon color and bring org owner to top of list
* lint + other fixes
* Revamp feature flag system, add flag config page
* Add button to flags page in dev mode
* fix env overrides
* make typescript happy with the refs
* new settings work
* Polishing work on settings refactor
* Run intl:extract
* List view -> Rows view
* Remove current preferred system theme indicator to make the themes fit on one line
* Remove extra margin on top of navstack
* Convert default.vue to composition API
* Add translations to default page layout
* Generate index.json
* Fix sign up page
* Generate index.json
* Fix atUserLabel
* Fix composition API port
* Follow-up fixes for #1616 (#1618)
* Re-organize default layout messages
- Group some of the messages by their appearance (like banners)
Grouping makes avoids having to think too much about the property
names, keeps declarations clean, and also can be minified better,
since variable names, unlike property names, can be easily mangled.
- Remove needless type specification in property name[^1]
It's already clear from where the message is formatted what it does,
and if you need clarification, you can Ctrl+hover and see the type in
the key.
- Change some keys to conform to conventions
We generally follow the pattern location > kind?. Things like 'label'
are unnecessary, as everything is assumed to be label by default; the
same applies to things like 'button', which are also often unnecessary
as they're part of the location compound.
- Remove message for handle, which should not be translatable
It's very unlikely user handle format changes between any of the
locales.
[^1]: Common messages are pending restructuring that would fix this
* Fix navRoutes not being computed in default layout
* Fix untranslated Get Modrinth App buttons in default layout
* Make legal disclaimer in the default layout translatable
It wouldn't make much sense to leave it untranslated since it is meant
for the end users too. It is also so small that it's unlikely to be
mistranslated.
* Extract missed legal disclaimer message from default layout
* Make SEO strings in default layout translatable
---------
Co-authored-by: Sasha Sorokin <10401817+brawaru@users.noreply.github.com>
* Begin Work
* More work
* Fix lint error
* More work on label
* Fix mistake
* Finish adding delete pat modal keys
* More label and button
* More label keys
* Fix lint error
* Description key
* Finish page
* Forgot this
* Fix lint error
* Add to navstack
* Apply suggestions from brawaru
* Normalization
* Re-organize PATs page messages (#10)
- Group messages by their usage
- Fix spelling mistakes in some of the property names and keys
- Change some of the keys to conform to keying conventions
- Change variable name in token.expires-in message to inTime
* Regenrate index.json
---------
Co-authored-by: Sasha Sorokin <10401817+brawaru@users.noreply.github.com>
