Skip to content
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

The right way to make a build #482

Open
yordanoff opened this issue Feb 22, 2019 · 3 comments
Open

The right way to make a build #482

yordanoff opened this issue Feb 22, 2019 · 3 comments

Comments

@yordanoff
Copy link

Hello,

what is the right way to build a static version of a Catalog?

Is it npm run catalog-build? Because it makes a /build folder where the JS files in the index.html are not being loaded. Do I miss something?

Thank you

@ranzen
Copy link

ranzen commented May 21, 2019

I experience the same problem. Any help appreciated

@yordanoff
Copy link
Author

yordanoff commented May 21, 2019

@ranzen check this out: https://twitter.com/yordanoff/status/1100357477206556672 and more specifically: #483

@Burning-Panda
Copy link

If anyone is still having this issue.
There exists a way to change the path so you can place the standalone in any folder.
At least as far as I know in v3.6.0

To build with relative paths use this command.
catalog build -u "./"

Found after looking at
node_modules\catalog\dist\cli\bin

Burning-Panda added a commit to Burning-Panda/catalog that referenced this issue Oct 27, 2020
As there is no explenation as to the options available when building the standalone app, I am proposing to add a short bit about how to build the standalone app and include how to change the static path to relative.

See issue interactivethings#482 and interactivethings#483
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants