dooboolab-community / dooboo-cli Goto Github PK
View Code? Open in Web Editor NEWEasily creates feature set in Expo and Expo Router.
Home Page: https://medium.com/dooboolab/the-new-dooboo-cli-693ac2413ba6
License: MIT License
Easily creates feature set in Expo and Expo Router.
Home Page: https://medium.com/dooboolab/the-new-dooboo-cli-693ac2413ba6
License: MIT License
🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨
To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.
Since we didn’t receive a CI status on the greenkeeper/initial
branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.
If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/
.
Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.
0.1.3
to 0.1.4
.This version is covered by your current version range and after updating it in your project the build failed.
@dooboo/eslint-config is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
9.1.0
to 9.2.0
.This version is covered by your current version range and after updating it in your project the build failed.
eslint-plugin-node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 9 commits.
9fbdaec
🔖 9.2.0
c1d5dbf
✨ add no-callback-literal rule (#179)
72de3a3
🐛 vulnerability fix: update eslint-utils to ^1.4.2 & eslint-plugin-es to ^1.4.1 (fixes #180) (#183)
cfc6352
🎨 fix typos in function names (#177)
b757c3e
⚒ improve azure-pipelines.yml (#173)
a85d541
⚒ trivial fix
88829af
⚒ Update azure-pipelines.yml for codecov (#170)
5b3f815
🐛 fix for ESLint 6 (#169)
fe73872
⚒ Switch to Azure Pipelines (#168)
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
4.0.1
to 4.0.2
.This version is covered by your current version range and after updating it in your project the build failed.
ora is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
It is recommended officially at the react-native document site.
And installed global react-native-cli
package may cause unexpected issues when using react-native-cli
with npx.
So I think that we should use npx to initialize react-native apps and stop requiring install 'react-native-cli' globally.
Currently, there's no keyword at all. If we set some keywords in package.json, it would be better for people to find dooboolab packages.
Some keywords I suggest are react, react-native, typescript, flow, mobx, boilerplate, cli, template.
Above all, thank you for the update.
I installed 'dooboo-cli 1.4.0'
And I used React Native App (typescript, context-api) mode
In this case, an app is always created with the name 'dooboo'.
The name of the directory is correct, but the app's name is always 'dooboo'.
The 1.3.x version and Legacy Mode operate correctly.
Thank you.
Hi, I've installed dooboo-cli
globally using yarn, but I'm having trouble using the cli globally on windows 10. It's not recognized as an internal or external command! Do I have to add an env system variable or something? If so, what's the path
? Thanks!
Actually just found out that the issue im running into has nothing to do with the operating system. It seems that the cli is broken in the latest version 8.4.2
.
import { EXPO_PROJECT_BRANCH, RN_PROJECT_BRANCH } from './const';
^^^^^^
SyntaxError: Cannot use import statement outside a module
at Object.compileFunction (node:vm:352:18)
at wrapSafe (node:internal/modules/cjs/loader:1031:15)
at Module._compile (node:internal/modules/cjs/loader:1065:27)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
at Module.load (node:internal/modules/cjs/loader:981:32)
at Function.Module._load (node:internal/modules/cjs/loader:822:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
at node:internal/main/run_main_module:17:47
If i downgrade it to 7.7.2
, it works fine!
When I have not installed Cocoapods and tried to initialize rn project, dooboo-cli asked me if I want to install Cocoapods. But the program did not respond even if I pressed Y key or n key or any other keys. Of course, it worked normally after I installed Cocoapods on it. But, I think we need to add a notice to the README.md file that asks us to install the cocoa pod first.
🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨
To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.
Since we didn’t receive a CI status on the greenkeeper/initial
branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.
If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/
.
Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.
I wrote a shell script to generate boilerplate for util/Icons.ts
I forked this project but cannot find how can I add this feature.
Can you suggest any idea for adding a feature to this repository?
generates
import BACK from '../../assets/icons/back.png';
import CLOSE from '../../assets/icons/close.png';
import MASK from '../../assets/icons/mask.png';
import MyName from '../../assets/icons/myName.svg';
export const IC_BACK = BACK;
export const IC_CLOSE = CLOSE;
export const IC_MASK = MASK;
export const SVGMyName = MyName;
I think this is a useful feature for boilerplate
package.json
"icon": "sh ./script/image_generate.sh ./assets/icons ./src/utils/Icons.ts",
script/icon_constant.sh
# arguments parse
ASSET_DIRECTORY=$1
ICON_FILE=$2
EXCLUDE_REGEX="@3x|@2x"
ICON_FILECOUNT=0
SVG_FILECOUNT=0
# general asset
declare -a ICON_KEY_ARRAY
declare -a ICON_CONST_ARRAY
declare -a ICON_PATH_ARRAY
# svg asset
declare -a SVG_KEY_ARRAY
declare -a SVG_CONST_ARRAY
declare -a SVG_PATH_ARRAY
for image in "$ASSET_DIRECTORY"/*
do
# filter multiplied images
if [[ $image =~ $EXCLUDE_REGEX ]] ; then
continue
fi
# filter directory or empty file
if [[ -d "$image" ]] || ! [[ -s "$image" ]] ; then
continue;
fi
# parse image name
assetExtension="${image##*.}" # extension
assetNameWithExtension="${image##*/}" # filename + extension without path (after last '/' in path)
assetName="${assetNameWithExtension%.*}" # filename without extension
# capitlize assetName if svg file or uppercase
if [[ $assetExtension =~ "svg" ]] ; then
capitlizedAssetName="$(tr '[:lower:]' '[:upper:]' <<< ${assetName:0:1})${assetName:1}"
variableName="SVG${capitlizedAssetName}"
SVG_KEY_ARRAY[$SVG_FILECOUNT]=$capitlizedAssetName
SVG_CONST_ARRAY[$SVG_FILECOUNT]=$variableName
SVG_PATH_ARRAY[$SVG_FILECOUNT]=$(realpath --relative-to="$(dirname $ICON_FILE)" $image)
SVG_FILECOUNT=$(expr $SVG_FILECOUNT + 1)
else
upperCasedAssetName=$(echo "$assetName" | tr "[:lower:]" "[:upper:]")
variableName="IC_${upperCasedAssetName}"
ICON_KEY_ARRAY[$ICON_FILECOUNT]=$upperCasedAssetName
ICON_CONST_ARRAY[$ICON_FILECOUNT]=$variableName
ICON_PATH_ARRAY[$ICON_FILECOUNT]=$(realpath --relative-to="$(dirname $ICON_FILE)" $image)
ICON_FILECOUNT=$(expr $ICON_FILECOUNT + 1)
fi
done
rm temp_image
touch temp_image
for ((i=0; i<ICON_FILECOUNT; i++)); do
echo "import ${ICON_KEY_ARRAY[i]} from '${ICON_PATH_ARRAY[i]}';" >> temp_image
done
for ((i=0; i<SVG_FILECOUNT; i++)); do
echo "import ${SVG_KEY_ARRAY[i]} from '${SVG_PATH_ARRAY[i]}';" >> temp_image
done
echo "" >> temp_image
for ((i=0; i<ICON_FILECOUNT; i++)); do
echo "export const ${ICON_CONST_ARRAY[i]} = ${ICON_KEY_ARRAY[i]};" >> temp_image
done
echo "" >> temp_image
for ((i=0; i<SVG_FILECOUNT; i++)); do
echo "export const ${SVG_CONST_ARRAY[i]} = ${SVG_KEY_ARRAY[i]};" >> temp_image
done
cp temp_image $ICON_FILE
rm -rf temp_image
I'm facing an error [ERR_UNKNOWN_FILE_EXTENSION] after installing 8.4.0
How can I fix it ?
node:internal/errors:464
ErrorCaptureStackTrace(err);
^
TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".json" for /usr/local/lib/node_modules/dooboo-cli/lib/package.json
at new NodeError (node:internal/errors:371:5)
at Object.getFileProtocolModuleFormat [as file:] (node:internal/modules/esm/get_format:87:11)
at defaultGetFormat (node:internal/modules/esm/get_format:102:38)
at defaultLoad (node:internal/modules/esm/load:21:14)
at ESMLoader.load (node:internal/modules/esm/loader:359:26)
at ESMLoader.moduleProvider (node:internal/modules/esm/loader:280:58)
at new ModuleJob (node:internal/modules/esm/module_job:66:26)
at ESMLoader.#createModuleJob (node:internal/modules/esm/loader:297:17)
at ESMLoader.getModuleJob (node:internal/modules/esm/loader:261:34)
at async ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:81:21) {
code: 'ERR_UNKNOWN_FILE_EXTENSION'
}
Hello.
I just created a react project using dooboo-cli (v3.6.1), installed the package, and ran yarn lint.
Then I got several errors as below.
1:8 error 'React' was used before it was defined no-use-before-define
I didn't change any codes after creating a project using dooboo-cli.
How can I fix them ?
6.4.0
to 6.5.0
.This version is covered by your current version range and after updating it in your project the build failed.
eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
73596cb
Update: Add enforceForSwitchCase option to use-isnan (#12106) (Milos Djermanovic)d592a24
Fix: exclude \u000d
so new line won't convert to text (fixes #12027) (#12031) (zamboney)e85d27a
Fix: no-regex-spaces false positives and invalid autofix (fixes #12226) (#12231) (Milos Djermanovic)b349bf7
Fix: prefer-named-capture-group incorrect locations (fixes #12233) (#12247) (Milos Djermanovic)7dc1ea9
Fix: no-useless-return autofix removes comments (#12292) (Milos Djermanovic)0e68677
Fix: no-extra-bind autofix removes comments (#12293) (Milos Djermanovic)6ad7e86
Fix: no-extra-label autofix removes comments (#12298) (Milos Djermanovic)acec201
Fix: no-undef-init autofix removes comments (#12299) (Milos Djermanovic)d89390b
Fix: use async reading of stdin in bin/eslint.js (fixes #12212) (#12230) (Barrie Treloar)334ca7c
Update: no-useless-rename also reports default values (fixes #12301) (#12322) (Kai Cataldo)41bfe91
Update: Fix handling of chained new expressions in new-parens (#12303) (Milos Djermanovic)160b7c4
Chore: add autofix npm script (#12330) (Kai Cataldo)04b6adb
Chore: enable eslint-plugin-jsdoc (refs #11146) (#12332) (Kai Cataldo)9b86167
Docs: Add new ES environments to Configuring ESLint (#12289) (Milos Djermanovic)c9aeab2
Docs: Add supported ECMAScript version to README (#12290) (Milos Djermanovic)8316e7b
Fix: no-useless-rename autofix removes comments (#12300) (Milos Djermanovic)29c12f1
Chore: cache results in runtime-info (#12320) (Kai Cataldo)f5537b2
Fix: prefer-numeric-literals autofix removes comments (#12313) (Milos Djermanovic)11ae6fc
Update: Fix call, new and member expressions in no-extra-parens (#12302) (Milos Djermanovic)a7894eb
New: add --env-info flag to CLI (#12270) (Kai Cataldo)61392ff
Sponsors: Sync README with website (ESLint Jenkins)2c6bf8e
Docs: English fix (#12306) (Daniel Nixon)6f11877
Sponsors: Sync README with website (ESLint Jenkins)2e202ca
Docs: fix links in array-callback-return (#12288) (Milos Djermanovic)e39c631
Docs: add example for CLIEngine#executeOnText 3rd arg (#12286) (Kai Cataldo)d4f9a16
Update: add support for JSXFragments in indent rule (fixes #12208) (#12210) (Kai Cataldo)c6af95f
Sponsors: Sync README with website (ESLint Jenkins)8cadd52
Sponsors: Sync README with website (ESLint Jenkins)f9fc695
Chore: enable default-param-last (#12244) (薛定谔的猫)9984c3e
Docs: Update README team and sponsors (ESLint Jenkins)The new version differs by 32 commits.
76fb571
6.5.0
7359a80
Build: changelog update for 6.5.0
73596cb
Update: Add enforceForSwitchCase option to use-isnan (#12106)
d592a24
Fix: exclude \u000d
so new line won't convert to text (fixes #12027) (#12031)
e85d27a
Fix: no-regex-spaces false positives and invalid autofix (fixes #12226) (#12231)
b349bf7
Fix: prefer-named-capture-group incorrect locations (fixes #12233) (#12247)
7dc1ea9
Fix: no-useless-return autofix removes comments (#12292)
0e68677
Fix: no-extra-bind autofix removes comments (#12293)
6ad7e86
Fix: no-extra-label autofix removes comments (#12298)
acec201
Fix: no-undef-init autofix removes comments (#12299)
d89390b
Fix: use async reading of stdin in bin/eslint.js (fixes #12212) (#12230)
334ca7c
Update: no-useless-rename also reports default values (fixes #12301) (#12322)
41bfe91
Update: Fix handling of chained new expressions in new-parens (#12303)
160b7c4
Chore: add autofix npm script (#12330)
04b6adb
Chore: enable eslint-plugin-jsdoc (refs #11146) (#12332)
There are 32 commits in total.
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Recently, I installed dooboo-cli and run it then below error messages are displayed.
/Users/buba1/.config/yarn/global/node_modules/dooboo-cli/lib/utils/functions.js:16
const chalk_1 = __importDefault(require("chalk"));
^
Error [ERR_REQUIRE_ESM]: require() of ES Module /Users/buba1/.config/yarn/global/node_modules/dooboo-cli/node_modules/chalk/source/index.js from /Users/buba1/.config/yarn/global/node_modules/dooboo-cli/lib/utils/functions.js not supported.
Instead change the require of index.js in /Users/buba1/.config/yarn/global/node_modules/dooboo-cli/lib/utils/functions.js to a dynamic import() which is available in all CommonJS modules.
at Object.<anonymous> (/Users/buba1/.config/yarn/global/node_modules/dooboo-cli/lib/utils/functions.js:16:33)
at Object.<anonymous> (/Users/buba1/.config/yarn/global/node_modules/dooboo-cli/lib/bin/root.js:18:21) {
code: 'ERR_REQUIRE_ESM'
}
Node.js v17.2.0
How can I resolve it?
안녕하세요.
아직까지 dooboo-cli 설치의 장벽을 못 넘고 있습니다.
mac이 없다보니, windows에서 하다가 실패하고,
aws ec2에서 해 봤습니다.
아래와 같이 했는데, 설치가 안됩니다. aws ec2가 centos 계열이라고 들었는데, 이때는 좀 다른 방법을 해 줘야 할까요?
sungyong:~/environment $ npm install -g react-native-cli
/home/ec2-user/.nvm/versions/node/v10.4.1/bin/react-native -> /home/ec2-user/.nvm/versions/node/v10.4.1/lib/node_modules/react-native-cli/index.js
+ [email protected]
updated 1 package in 1.045s
sungyong:~/environment $ npm install -g dooboo-cli
npm WARN [email protected] requires a peer of react-native-cli@* but none is installed. You must install peer dependencies yourself.
npm ERR! path /home/ec2-user/.nvm/versions/node/v10.4.1/lib/node_modules/dooboo-cli/bin/root.js
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall chmod
npm ERR! enoent ENOENT: no such file or directory, chmod '/home/ec2-user/.nvm/versions/node/v10.4.1/lib/node_modules/dooboo-cli/bin/root.js'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! A complete log of this run can be found in:
npm ERR! /home/ec2-user/.npm/_logs/2018-07-10T12_43_14_995Z-debug.log
/home/ec2-user/.npm/_logs/2018-07-10T12_43_14_995Z-debug.log 의 내용은 아래와 같습니다.
4605 warn [email protected] requires a peer of react-native-cli@* but none is installed. You must install peer dependencies yourself.
4606 verbose stack Error: ENOENT: no such file or directory, chmod '/home/ec2-user/.nvm/versions/node/v10.4.1/lib/node_modules/dooboo-cli/bin/root.js'
4607 verbose cwd /home/ec2-user/environment
4608 verbose Linux 4.14.42-52.37.amzn1.x86_64
4609 verbose argv "/home/ec2-user/.nvm/versions/node/v10.4.1/bin/node" "/home/ec2-user/.nvm/versions/node/v10.4.1/bin/npm" "install" "-g" "dooboo-cli"
4610 verbose node v10.4.1
4611 verbose npm v6.1.0
4612 error path /home/ec2-user/.nvm/versions/node/v10.4.1/lib/node_modules/dooboo-cli/bin/root.js
4613 error code ENOENT
4614 error errno -2
4615 error syscall chmod
4616 error enoent ENOENT: no such file or directory, chmod '/home/ec2-user/.nvm/versions/node/v10.4.1/lib/node_modules/dooboo-cli/bin/root.js'
4617 error enoent This is related to npm not being able to find a file.
4618 verbose exit [ -2, true ]
2.5.0
to 2.6.0
.This version is covered by your current version range and after updating it in your project the build failed.
update-notifier is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
The new version differs by 10 commits.
622ee5f
2.6.0
ad8ed1b
Suggest yarn when installed with yarn (#132)
5f06620
Exit the update check process if it does not respond after 30s (#156)
79e89ad
Fix failing test (#155)
c8faa84
Add distTag
option (#151)
14632e4
Add failing test for #153 (#154)
aafd8a0
Require Node.js 8
0d49f51
Add Tidelift mention in the readme
8df01b3
Fix docs position of shouldNotifyInNpmScript
(#143)
d371834
Docs: isGlobal option does not default to true (#142)
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
🚨 You need to enable Continuous Integration on all branches of this repository. 🚨
To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.
Since we didn’t receive a CI status on the greenkeeper/initial
branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.
If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/
.
Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial
branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.
0.1.7
to 0.1.8
.This version is covered by your current version range and after updating it in your project the build failed.
@dooboo/eslint-config is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
12.12.13
to 12.12.14
.This version is covered by your current version range and after updating it in your project the build failed.
@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Related with this issues
I tried to Expo project with dooboo-cli
first time.
After then, this warning appears.
Accessing view manager configs directly off UIManager via UIManager['getConstants'] is no longer supported. Use UIManager.getViewManagerConfig('getConstants') instead.
So I did like this.
yarn remove react-native-gesture-handler
expo install react-native-gesture-handler
dooboo start
Then, the warning is not appears to me.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.