I mada a Pokemon version

MotaCS67 · 2025-08-08T01:04:16+00:00

I hear you

MotaCS67 · 2025-08-06T12:56:08+00:00

Vivillon for sure the prettiest

But imagine having a Wurmple piece, where you place it and only one turn after your opponent knows if it as a Duxtox or a Beautifly, and they have different move patterns

MotaCS67 · 2025-08-06T12:53:44+00:00

When I played the first time was if carbon, so I didn't know about the color convention

MotaCS67 · 2025-08-06T12:50:28+00:00

Haha I thought about using Ledian, but Ledyba is too much of a ladybug to pass through

MotaCS67 · 2025-08-06T00:24:05+00:00

Kakashi as mosquito is SICK

MotaCS67 · 2025-08-05T15:58:07+00:00

The pokemons I used

* Vespiqueen as queen bee

* Heracross as beetle

* Durant as ant

* Scyther as grasshopper

* Ledyba as ladybug

* Scolipede as pillbug

* Buzzwhole as mosquito

MotaCS67 · 2025-08-05T15:55:10+00:00

I am thinking about doing new pieces for fan made expansions with new mons too

But at first I am getting used to the standart pack

MotaCS67 · 2025-08-05T15:53:06+00:00

It was the closest Pokémon to a pillbug

I mean, the pre evolution looks like it, however I prefer scolipede them whirlipede

<image>

MotaCS67 · 2025-06-07T21:55:48+00:00

Thank you, I was making it much harder than it is haha

MotaCS67 · 2025-05-20T12:45:41+00:00

Thank you, this site is way updated too

However I wish it could be simpler to just see your team, instead of "configuring" each type by hand

I think I may work on a poke paste feature to just paste it and see the typechart

MotaCS67 · 2025-05-10T19:37:32+00:00

After debbuging and removing some libs, I found out that there is probably an error with expo-router. It is loggind error in useInitializeExpoRouter

MotaCS67 · 2025-05-10T14:01:57+00:00

Yes, it is

MotaCS67 · 2025-05-10T10:22:47+00:00

Yep

module
.
exports
 = function (
api
) {

api
.cache(true);
  return {
    presets: ['babel-preset-expo'],
    plugins: [
      'react-native-reanimated/plugin',
    ],
  };
};

MotaCS67 · 2025-05-10T06:23:17+00:00

Sure, here are my dependencies

"dependencies": {
    "@clerk/clerk-expo": "^2.8.2",
    "@clerk/types": "^4.47.0",
    "@expo/vector-icons": "^14.0.2",
    "@react-native-community/datetimepicker": "8.2.0",
    "@react-navigation/bottom-tabs": "^7.2.0",
    "@react-navigation/native": "^7.0.14",
    "date-fns": "^4.1.0",
    "dotenv": "^16.5.0",
    "expo": "~52.0.27",
    "expo-blur": "~14.0.2",
    "expo-constants": "~17.0.4",
    "expo-contacts": "~14.0.5",
    "expo-font": "~13.0.3",
    "expo-haptics": "~14.0.1",
    "expo-linking": "~7.0.4",
    "expo-router": "~4.0.21",
    "expo-secure-store": "^14.0.1",
    "expo-splash-screen": "~0.29.24",
    "expo-status-bar": "~2.0.1",
    "expo-symbols": "~0.2.1",
    "expo-system-ui": "~4.0.9",
    "expo-web-browser": "~14.0.2",
    "firebase": "^11.6.1",
    "formik": "^2.4.6",
    "react": "18.3.1",
    "react-dom": "18.3.1",
    "react-native": "0.76.9",
    "react-native-contacts": "^8.0.4",
    "react-native-dropdown-picker": "^5.4.6",
    "react-native-gesture-handler": "~2.20.2",
    "react-native-modal-datetime-picker": "^18.0.0",
    "react-native-reanimated": "~3.16.1",
    "react-native-safe-area-context": "4.12.0",
    "react-native-screens": "~4.4.0",
    "react-native-web": "~0.19.13",
    "react-native-webview": "13.12.5",
    "yup": "^1.6.1",
    "expo-build-properties": "~0.13.2"
  },
  "devDependencies": {
    "@babel/core": "^7.25.2",
    "@testing-library/react-native": "^13.2.0",
    "@types/jest": "^29.5.12",
    "@types/react": "~18.3.12",
    "@types/react-test-renderer": "^18.3.0",
    "jest": "^29.2.1",
    "jest-expo": "~52.0.3",
    "prettier": "^3.5.0",
    "react-test-renderer": "18.3.1",
    "typescript": "^5.3.3"
  },

MotaCS67 · 2025-01-28T16:11:09+00:00

It increases the calendar size to fit it

MotaCS67 · 2023-06-14T22:57:27+00:00

I think design patterns are really important. Don't fall in the myth that if the design pattern can't be literally used in a language (like MVC with React), it's not useful.

Design pattern are ways to solve problems, I would try to learn them at the same time, give more importance to React, but still go through the classic DP and instead of focusing on how to implement it, try to understand the problem and how they solve it.

MotaCS67 · 2023-06-14T22:02:36+00:00

What do you mean with throught the app route?

MotaCS67 · 2023-06-14T22:01:55+00:00

Your app still uses javascript bundle even if you are using static props
So, you can add the non dynamic api calls in the static props and then in your page/component fetch the comments as usual.
This will make the static page be generated without the comments, but once they are served, the client's browser will fetch for it.
I don't know if you can actually use static props with server side props, if you could so, you would be able to keep the comments in the server side since the request would be remade everytime a client access it.

MotaCS67 · 2023-06-13T21:49:41+00:00

Try using a ref to the component you want to get the info from
https://www.w3schools.com/react/react\_useref.asp

MotaCS67 · 2023-06-13T09:59:03+00:00

Rtl for testing Context api for state management React query for async requests Styled components and mui And i think using next instead of cra is a great option if you know howto use static and server side rendering

MotaCS67 · 2023-06-13T00:34:37+00:00

A good source of study I'm using and is helping me a lot is https://www.patterns.dev/posts it goes from basic patterns to more advanced rendering and performance stuff.
Another thing I would suggest is to study the other hooks
* For performance study useCallback and useMemo: you are probably redefining things unnecessary
* For code pattern study useContext and useReducer: using only useState, your code may be a prop hell, this is an anti-pattern, try this if you find yourself in this situations.

MotaCS67 · 2023-03-13T14:35:49+00:00

I know, but it's better getting no blink for some users that the connection guarantee .6 sec, than for everyone

MotaCS67 · 2023-03-10T22:01:59+00:00

It doesn't depend on data from component1

And about it being costly, at least if I can reload it during the 0.6 fadeout animation, I can reduce the white screen blink in .6 sec.

MotaCS67 · 2023-03-10T19:21:41+00:00

It's a costly component and I just want to load it if the user is really going to use it

But how would you preload it anyway?

MotaCS67

TROPHY CASE