#@inlang/paraglide-js
#1.11.3
#Patch Changes
- e04d5fe: Update dependency
- a1ea1ff: fix internal issues
- fa42a3a: Include paraglide version in reporting
#1.11.2
#Patch Changes
- 59c8b11: Fix Ninja recommendation and adoption if working directory is not the repo root
#1.11.1
#Patch Changes
-
14d80b3: Removed the "Which tech-stack are you using?" prompt from the
init
command as it was not providing any real value. All it did was link you to the appropriate documentation.From now on we rely on the docuemntation site to guide people to the correct documenation for their framework.
- SvelteKit: https://inlang.com/m/dxnzrydw/paraglide-sveltekit-i18n
- NextJs: https://inlang.com/m/osslbuzt/paraglide-next-i18n
- Astro: https://inlang.com/m/iljlwzfs/paraglide-astro-i18n
- SolidStart: https://inlang.com/m/n860p17j/paraglide-solidstart-i18n
- Vite: https://github.com/opral/monorepo/tree/main/inlang/source-code/paraglide/paraglide-vite
#1.11.0
#Minor Changes
- e37eabf: - renamed packages
@inlang/cross-sell-X
to@inlang/recommend-X
be more descriptive- refactor recommendation view in Sherlock VS Code extension
- introduce new
shouldRecommend
function to@inlang/recommend-sherlock
&@inlang/recommend-ninja
#1.10.1
#Patch Changes
- c5d145d: use types from SDK for error handling
#1.10.0
#Minor Changes
- 33662e6: Gracefully handle errors in the Inlang Project. Only crash on errors that are fatal to paraglide specifically
#1.9.1
#Patch Changes
- b8573fa: Improved error-reporting
#1.9.0
#Minor Changes
- eb941fe: Prompt about adding the Ninja Github Action for translation-linting during
paraglide-js init
. Also exposes it over the internal API.
#Patch Changes
- 9566348: Better handling of
tsconfig
files thatextends
another config.
#1.8.0
#Minor Changes
- 21ab0a0: Add an output mode where each message is it's own file. This enables treeshaking in less capable bundlers. Currently this is only available via the programmatic API.
#Patch Changes
- 21ab0a0: performance improvements
#1.7.3
#Patch Changes
- 32cbe48: Improve
bestMatch
reliability
#1.7.2
#Patch Changes
- 6105a50: No longer log "Exiting the Watcher" when stopping the watching process, as it was causing annoying CMD popups on windows
#1.7.1
#Patch Changes
- 4d24188:
paraglide-js init
now uses thecreateNewProject
API from@inlang/sdk
for creating new projects. This resulits in higher reliability.
#1.7.0
#Minor Changes
- 0774c1a: Expose CLI programmatically to enable framework-specific init clis
#1.6.2
#Patch Changes
- cee4692: Use index accesses instead of
.at
function for better compatability with legacy browsers - 4b631aa: Update invalid type-declarations
- 3c7a87c: Fixes a race-condition when creating the messages directory during
paraglide-js init
- ab1fe48: When initialising and a single project is available, it no longer suggests and empty string as the project path
#1.6.1
#Patch Changes
- fa6aa31: Update internal adapter-utilities
- dee5aa6: Add
--silent
option toparaglide-js compile
command that will only log errors
#1.6.0
#Minor Changes
- 462325b: Paraglide now ships with internal utility functions that handle common adapter tasks such as language-negotiation. These aren't public facing, but the version bump is required to make sure adapter-packages resolve the correct version of paragldie.
#1.5.0
#Minor Changes
- 2428451:
paraglide-js init
now finds more existing projects
#1.4.0
#Minor Changes
- d47b2aa: Generate empty
messages/{lang}.js
files if no messages are present. This way the "shape" of the generated output is always the same regardless of messages
#Patch Changes
- 192fdec: prompt the user for the
outdir
duringparaglide-js init
- 0b7c82e: Inline package-version at build time to be more robust
#1.3.7
#Patch Changes
- 1cc9cbc: Run compiler after
paraglide-js init
so that initial files are present - 5401f95: Add
--outdir
flag to the generated CLI commands
#1.3.6
#Patch Changes
- 526b0ba:
paraglide-js init
now prompts for which languages should be supported - 26d2ba1: No longer add
identical-pattern
lint rule by default
#1.3.5
#Patch Changes
- 7dce581: fix
openRepository
crash in non-git environments
#1.3.4
#Patch Changes
- 2a42b6e: bump
@lix-js/client
dependency
#1.3.3
#Patch Changes
- 11f0e18: Update dependency
- 10e3c28: fix JSDoc annotations on message aliases
#1.3.2
#Patch Changes
- 45975c0: Fail gracefully if adding
.vscode
folder fails
#1.3.1
#Patch Changes
- afaaffa: Bundle
@inlang/recommend-sherlock
. This is used to promot once duringparaglide-js init
to ask if you want to install the Sherlock vscode extension
#1.3.0
#Minor Changes
- 4970afc: paraglide deprecate aliases
- 4837297: File locking for concurrent message updates through the load/store plugin api Auto-generated human-IDs and aliases - only with experimental: { aliases: true }
#Patch Changes
- @inlang/recommend-sherlock@0.0.2
#1.2.9
#Patch Changes
- a99e35fee: use
@inlang/recommend-sherlock
during vscode extension initialization - Updated dependencies [a99e35fee]
- @inlang/recommend-sherlock@0.0.2
#1.2.8
#Patch Changes
- b0f1e908b: Prompt user for tech-stack when running
paraglide-js init
& recommend Adapters
#1.2.7
#Patch Changes
- f6ec6cdc9: bump
@inlang/sdk
dependency
#1.2.6
#Patch Changes
- 960f8fb70: rename the vscode extension to "Sherlock"
#1.2.5
#Patch Changes
- 00f181ad3: fix broken dependency
#1.2.4
#Patch Changes
- Updated dependencies [244442698]
- @inlang/language-tag@1.5.0
#1.2.3
#Patch Changes
- 4c26fa70a: bump dependencies
#1.2.2
#Patch Changes
- 613ef9877: fix: Bump
@lix-js/client
dependency
#1.2.1
#Patch Changes
- 74dc1f8c6: Update dependencies
- 4ae6295d0: Detect when
paraglide-js init
is being run inside the VsCode terminal and skip the VsCode question if so - Updated dependencies [74ac11c47]
- @inlang/language-tag@1.4.0
#1.2.0
#Minor Changes
- 0f0e8496d: Throw runtime error if
languageTag()
returns a non-language tag value
#1.1.1
#Patch Changes
- 7ea9753fb: Improve onboarding message
- 4277232db: fix: better formatting of messageID fallbacks
#1.1.0
#Minor Changes
- cd29edb11: bumbing fixed env var dependecy issue affected packages
#1.0.0
Bump Version to 1.0 as no more breaking changes are expected.
#1.0.0-prerelease.26
Hotfix: Bundle SDK
#1.0.0-prerelease.25
Update dependencies
#1.0.0-prerelease.24
feat: Support language Fallbacks according to BCP 47 specification
#1.0.0-prerelease.23
Update dependencies
#1.0.0-prerelease.22
Update dependencies
#1.0.0-prerelease.21
feat: Handle variables that have invalid JS identifiers as names. fix: Better text escaping in the compiler. fix: Compiler now fails reliably when a message ID is an invalid JS identifier.
#1.0.0-prerelease.20
Paraglide now checks if the messages have actually changed before recompiling. This should improve reliability and performance.
#1.0.0-prerelease.19
fix: Fix inlang/internal#195
#1.0.0-prerelease.18
paraglide-js init
now adds @inlang/message-lint-rule-valid-js-identifier
by default.
#1.0.0-prerelease.17
paraglide-js init
now adds paraglide-js compile
to the postinstall script by default. This sidesteps numerous linting issues when using paraglide in CI environments.
#1.0.0-prerelease.16
Fix paraglide-js compile
hanging for a couple seconds after successful compilation
#1.0.0-prerelease.15
Fix crash when using npx @inlang/paraglide-js init
and selecting vscode.
#1.0.0-prerelease.14
Added --watch
flag to the paraglide-js compile
command. This will keep the process alive and recompile whenever messages are changed.
paraglide-js compile --project ./project.inlang --watch
#1.0.0-prerelease.13
./paraglide/runtime.js
now exports a function called isAvailableLanguageTag
. This is
the recommended way to check if something is a valid language tag, while maintaining
type safety.
//Pseudo code
import { isAvailableLanguageTag } from "./paraglide/runtime"
if (isAvailableLanguageTag(params.lang)) {
return renderSite(params.lang)
} else {
return 404
}
#1.0.0-prerelease.12
[Internal Change] Expose the compiler so that bundler plugins can call it programmatically instead of going through the CLI.
#1.0.0-prerelease.11
onSetLanguageTag
no longer throws when called multiple times. Newer callbacks will overwrite old ones.
Developers still should not call onSetLanguageTag
multiple times, this is needed for HMR to work reliably.
Big thanks to @KraXen72
#1.0.0-prerelease.10
Add an optional options argument to message functions, to allow forcing a languageTag regardless of which languageTag is currently set.
import * as m from "./paraglide/messages"
const msg = m.hello({ name: "John" }, { languageTag: "de" })
#1.0.0-prerelease.9
The paraglide-js init
command now uses the inlang message format 2.0 which is human readable.
#1.0.0-prerelease.8
IMPROVE: Paraglide now splits messages into different resource files as a step towards splitting messages by language via a bundler plugin.
import * as en from "./paraglide/messages/en"
import * as de from "./paraglide/messages/de"
en.hello()
de.hello()
#1.0.0-prerelease.7
FIX: type error https://github.com/opral/monorepo/pull/1610#issuecomment-1801768825
export const currentLanguageTag = (params) => {
+ /** @type {Record<string, string>} */
const variants = {
en: `The current language tag is "${params.languageTag}".`,
de: `Der aktuelle Sprachtag ist "${params.languageTag}".`,
}
return variants[languageTag()] ?? "currentLanguageTag"
}
#1.0.0-prerelease.6
BREAKING: Paraglide JS now compiles into source code, see https://github.com/opral/monorepo/issues/1607
What you need to change:
- Remove
--namespace
from the compile command - Replace imports from paraglide to point to the directory in ther source code:
-import { setLanguageTag, languageTag } from '@inlang/paraglide-js/sveltekit-example';
+import { setLanguageTag, languageTag } from '../../paraglide-js/runtime';
-import * as m from "@inlang/paraglide-js/sveltekit-example/messages"
+import * as m from "../../paraglide-js/messages"
#1.0.0-prerelease.5
improve: paraglide-js init
now adds the Visual Studio Code extension (Sherlock) if vscode is used
#1.0.0-prerelease.4
add: paraglide-js init
command which simplifies the setup process
#1.0.0-prerelease.3
fix: https://github.com/opral/monorepo/issues/1478
#1.0.0-prerelease.1
#fix: Jetbrains based editors not detecting @inlang/paraglide-js/{namespace}/messages
imports
The bug has been fixed by moving ./*/messages
above the less specifc ./*
export.
"exports": {
"./*/messages": "./dist/compiled-output/*/messages.js",
"./*": "./dist/compiled-output/*/runtime.js"
},