-
Notifications
You must be signed in to change notification settings - Fork 58
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
Zip Command Fails On WAMP Environments #22
Comments
@richardginn That looks good. Is the plugin active under Plugins > Installed Plugins? |
NO!!! wants to bash head on the wall a few hundred times for not seeing it in the first placeNow I see it.... Now I will attempt to create a new module later on this week. |
Now for the YARN ZIP command is that an error we are supposed to see?? If it does .zip the module where does the ,zip file show up. |
@richardginn Looks like this is a bug. @lots0logs will look into it. In the meantime, when you are ready to package your plugin run
|
Thanks for listing the excludable files @VladET. That's super helpful in the interim. |
You are welcome, @SJ-James! 😃 |
Just a quick additional note, you should also exclude all the JSX files as wells as any non-minified scripts and styles. |
Opening the command line tool as administrator in Windows to run yarn zip works for me. |
I tried to get the SimpleHeader example to work though Xampp and I do not see a NEW module at all.
The first image is with yarn start....
Where can I view it in my browser??
This is what I see after doing Yarn Build.
Yet I still do not see a new module??
What am I do wrong while other people seem to have done it right??
Do I need more than just Xampp running at the same time?? I have yarn and nodejs installed,.
HELP!
UPDATE: This is what I see when I try yarn Zip...
Is this another looking for Wp-config.php file errors?? That would be in the htdocs directory for my windows 10 install of Xampp.
I am even including the includes directory here in a .zip file.
includes.zip
Any help here would be nice.
The text was updated successfully, but these errors were encountered: