goatandsheep / react-native-dotenv

Load react native environment variables using import statements for multiple env files.
https://www.npmjs.com/package/react-native-dotenv
MIT License
790 stars 47 forks source link

Caching issues still present #378

Closed elitenas closed 1 year ago

elitenas commented 1 year ago

Hi,

We are using the latest package for react-native-dotenv and we are still facing caching issues. We are using it with expo and typescript. Is there a way to clear the env variables cache?

github-actions[bot] commented 1 year ago

Hey, thank you for opening this issue! 🙂 To boost priority on this issue and support open source please tip the team at https://issuehunt.io/r/goatandsheep/react-native-dotenv/issues/378

goatandsheep commented 1 year ago

force babel to be up to date:

"resolutions": {
  "@babel/core": "^7.20.2",
  "babel-loader": "8.3.0"
}

then try safe mode

elitenas commented 1 year ago

I am getting the follow error now:

api.addExternalDependency is not a function

Here is what the dependencies part of my package.json looks like:

"dependencies": {
    "@eva-design/eva": "^2.1.1",
    "@expo/react-native-action-sheet": "^3.13.0",
    "@feathersjs/authentication-client": "^4.5.15",
    "@feathersjs/client": "^4.5.15",
    "@feathersjs/socketio-client": "^4.5.15",
    "@react-native-async-storage/async-storage": "~1.15.0",
    "@react-native-community/masked-view": "^0.1.11",
    "@react-native-community/slider": "~4.1.12",
    "@react-native-masked-view/masked-view": "0.2.6",
    "@react-native-picker/picker": "2.2.1",
    "@react-navigation/bottom-tabs": "^6.3.1",
    "@react-navigation/native": "^6.0.11",
    "@react-navigation/native-stack": "^6.6.2",
    "@react-navigation/stack": "^6.2.2",
    "@types/react": "17.0.2",
    "@types/react-dom": "17.0.2",
    "@ui-kitten/components": "^5.1.2",
    "@ui-kitten/eva-icons": "^5.1.2",
    "axios": "^0.27.2",
    "date-fns": "^2.28.0",
    "expo": "^44.0.6",
    "expo-av": "~11.0.0",
    "expo-dev-client": "~0.8.4",
    "expo-device": "~4.1.0",
    "expo-file-system": "~13.1.4",
    "expo-image-picker": "~12.0.1",
    "expo-localization": "~12.0.0",
    "expo-location": "~14.0.1",
    "expo-network": "~4.1.0",
    "expo-notifications": "~0.14.0",
    "expo-splash-screen": "~0.14.1",
    "expo-status-bar": "~1.2.0",
    "expo-updates": "~0.11.7",
    "feathers-errors": "^2.9.2",
    "i18next": "^21.8.11",
    "lodash": "^4.17.21",
    "moment-hijri": "^2.1.2",
    "react": "17.0.1",
    "react-dom": "17.0.1",
    "react-i18next": "^11.17.3",
    "react-native": "0.64.3",
    "react-native-gesture-handler": "~2.1.0",
    "react-native-gradient-buttons": "^2.0.2",
    "react-native-mmkv": "^2.2.0",
    "react-native-reanimated": "~2.3.1",
    "react-native-safe-area-context": "3.3.2",
    "react-native-screens": "~3.10.1",
    "react-native-svg": "^12.1.1",
    "react-native-ui-kitten": "^4.4.1",
    "react-native-vector-icons": "^9.2.0",
    "react-native-web": "0.17.1",
    "react-native-webview": "11.15.0",
    "react-navigation": "^4.4.4",
    "rn-bounceable": "^1.1.0",
    "sentry-expo": "^4.2.0",
    "sharp-cli": "^2.1.1",
    "socket.io-client": "^2.3.0",
    "yup": "^0.32.11"
  },
  "devDependencies": {
    "@babel/core": "^7.12.9",
    "@babel/plugin-proposal-class-properties": "^7.18.6",
    "@babel/preset-typescript": "^7.16.7",
    "@expo/config-plugins": "^4.1.0",
    "@expo/webpack-config": "~0.16.2",
    "@react-native-community/eslint-config": "2.0.0",
    "@types/i18n-js": "^3.8.2",
    "@types/lodash": "^4.14.180",
    "@types/react-native": "~0.64.12",
    "@typescript-eslint/eslint-plugin": "^5.15.0",
    "@typescript-eslint/parser": "^5.15.0",
    "dotenv-cli": "^5.0.0",
    "eslint": "7.14.0",
    "react-native-dotenv": "^3.4.2",
    "release-it": "^14.12.5",
    "typescript": "~4.3.5"
  },
  "resolutions": {
    "@babel/core": "^7.20.2",
    "babel-loader": "8.3.0"
  }
goatandsheep commented 1 year ago

Upgrade Babel core devdep

elitenas commented 1 year ago

Same result. I tried expo r -c to start it as well.

elitenas commented 1 year ago

Ah, I am using npm install instead of yarn. I will need to update my npm version because I think the npm 8.3.0 support this override.

goatandsheep commented 1 year ago

if you can nudge the devs on this PR it will probably help https://github.com/expo/expo-cli/pull/4593

but the other change that was merged was this https://github.com/expo/expo/pull/19829

i'm not sure how to get that in, but i guess expo should be up to date. sorry for the confusion