-
Notifications
You must be signed in to change notification settings - Fork 34
Start kit : Startup errors #24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
did you found any solution |
Any solutions for Tailwindcss taking long time to load? |
I also same issues for "Tailwindcss loading" |
@jvharyani @ksankkaaii i solved it changing tailwind.config.js for the next configuration. const gluestackPlugin = require('@gluestack-ui/nativewind-utils/tailwind-plugin'); /** @type {import('tailwindcss').Config} / theme: { |
I solved it with the following diffs. The "presets" key has a value of [null], which is unusual. If you're not using any presets, you can remove the presets key entirely. diff --git a/tailwind.config.js b/tailwind.config.js
index 5eb3a6b..1298f39 100644
--- a/tailwind.config.js
+++ b/tailwind.config.js
@@ -14,12 +14,6 @@ module.exports = {
"flex-wrap",
"mb-12",
"basis-[10%]",
- {
- "pattern": {}
- }
- ],
- "presets": [
- null
],
"theme": {
"screens": { Additionally, I had to |
For the first issue: Windows console doesn't let you set environment variables like that. I added the package
That fixes the environment variable problem. But ... it still only barely works. 😞 Maybe a lack of testing on Windows? Not sure. |
OH, and be sure to use the exact |
Hello,
I retrieved the project from the starter kit to test it with Expo.
At first, the "start" command with the "EXPO_USE_METRO_WORKSPACE_ROOT=1" argument is not recognized as an internal command. Can you tell me what it corresponds to and how to counter this behavior?
I thought about putting this argument in a .env file, but is that the solution?
I then encountered this error, which after several manipulations was countered, but does it sound familiar to you?
error: node_modules\expo-router\entry.js: You appear to be using a native ECMAScript module configuration file, which is only supported when running Babel asynchronously.
Additionally, while doing this process, I encountered a second issue. This time, Tailwindcss doesn't load, with the stack trace present below.
I tried updating all the libraries to their latest versions, but it had no effect on the result.
tailwindcss(android) rebuilding... tailwindcss(android) is taking a long time to build, please read https://tailwindcss.com/docs/content-configuration#pattern-recommendations to speed up your build time
Rebuilding... TypeError: Cannot read properties of undefined (reading 'includes') at C:\Users\user\Documents\VSCode\gluestack-ui-starter-kits\expo-app\node_modules\tailwindcss\lib\lib\setupContextUtils.js:852:81 at Array.some (<anonymous>) at registerPlugins (C:\Users\\user\Documents\VSCode\gluestack-ui-starter-kits\expo-app\node_modules\tailwindcss\lib\lib\setupContextUtils.js:852:46) at createContext (C:\Users\user\Documents\VSCode\gluestack-ui-starter-kits\expo-app\node_modules\tailwindcss\lib\lib\setupContextUtils.js:1221:5) at createContext (C:\Users\user\Documents\VSCode\gluestack-ui-starter-kits\expo-app\node_modules\tailwindcss\lib\processTailwindFeatures.js:44:61) at Object.getContext (C:\Users\user\Documents\VSCode\gluestack-ui-starter-kits\expo-app\node_modules\tailwindcss\lib\cli\build\plugin.js:200:24) at C:\Users\user\Documents\VSCode\gluestack-ui-starter-kits\expo-app\node_modules\tailwindcss\lib\cli\build\plugin.js:247:38 at C:\Users\user\Documents\VSCode\gluestack-ui-starter-kits\expo-app\node_modules\tailwindcss\lib\processTailwindFeatures.js:46:11 at Object.Once (C:\Users\user\Documents\VSCode\gluestack-ui-starter-kits\expo-app\node_modules\tailwindcss\lib\cli\build\plugin.js:255:19) at LazyResult.runOnRoot (C:\Users\user\Documents\VSCode\gluestack-ui-starter-kits\expo-app\node_modules\postcss\lib\lazy-result.js:327:23)
The text was updated successfully, but these errors were encountered: