-
Notifications
You must be signed in to change notification settings - Fork 555
feat: add install script #122
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
base: master
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
I got this error. yarn build |
@rogerznts on which yarn build and exact commit (Plasmic) does that happen? |
Thank you, this nice script 🚀 |
@kiyochinh does the script work for you? |
continue | ||
fi | ||
echo "Building... $dir" | ||
pushd platform/"$dir" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I got an error at this line:
Building... platform/canvas-packages
./install.bash: line 42: pushd: platform/platform/canvas-packages: No such file or directory
Since $dir
will already be prefixed with "platform/"
, I think this should be changed to:
echo "Building... $dir"
pushd "$dir"
pushd platform/"$dir" | ||
if [ -f package.json ]; then | ||
if [ "\$(jq -r '.scripts.build' package.json)" != "null" ]; then | ||
NODE_ENV=production yarn build |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I get the following error at this line:
Building... platform/integration-tests
~/Development/plasmic/platform/integration-tests ~/Development/plasmic
yarn run v1.22.22
error Command "build" not found.
I think this should be changed to remove the backslash on line 44, ie:
if [ -f package.json ]; then
if [ "$(jq -r '.scripts.build' package.json)" != "null" ]; then
NODE_ENV=production yarn build
This is the logic that our team derived from the the multi installations step and might be useful for others. Happy to simply also other parts of the community build process and deployment if you are interested in those.