generaltranslation 1.2.4 → 1.2.5

package/index.js

@@ -3,7 +3,6 @@
 
 // ----- IMPORTS ----- //
 
-import _getUserLanguage from "./client/getUserLanguage.js";
 import { _getLanguageCode, _getLanguageName } from "./codes/codes.js"
 import _translatePrompt from "./translate/prompts.js"
 import _createI18N from "./translate/html.js";
@@ -47,6 +46,5 @@ export default class GT {
 
 export {
     _getLanguageCode as getLanguageCode,
-    _getLanguageName as getLanguageName,
-    _getUserLanguage as getUserLanguage
+    _getLanguageName as getLanguageName
 };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "generaltranslation",
-  "version": "1.2.4",
+  "version": "1.2.5",
   "description": "A language toolkit for AI developers",
   "main": "index.js",
   "type": "module",

package/client/getUserLanguage.js

@@ -1,19 +0,0 @@
-// Returns a user's default browser language
-// e.g. 'en-US', not necessarily 'en'
-// generaltranslation handles this well, but other libraries may not
-// (it's a skill issue I'm afraid) 
-export default function _getUserLanguage({ defaultLanguage = '' } = {}) {
-    try {
-        if (window?.navigator?.language) {
-            return (window.navigator.language || defaultLanguage || '').toLowerCase();
-        }
-    } catch (error) {
-        if (defaultLanguage) {
-            return defaultLanguage.toLowerCase();
-        } else {
-            console.error("getUserLanguage error. It's likely you've called getUserLanguage() on the server. This is inadvisable and without a default language will return an empty string.")
-            return ''
-        }
-    }
-    
-}