We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
During the CARTOFrames 🔱 project we've realized there are some annoying discrepancies between where files are on the CDN and when you load locally.
libs.cartocdn.com/airship-components/<version>/<file> is <hostname>:<port>/packages/components/dist/file
libs.cartocdn.com/airship-components/<version>/<file>
<hostname>:<port>/packages/components/dist/file
Even worse, on the CDN, it's airship-style, and locally it's styles.
Using serve we can add rewrite rules so you can write urls like:
<hostname>:<port>/airship-components/<version>/<path> and rewrites to the correct file.
<hostname>:<port>/airship-components/<version>/<path>
There's an open PR that we need for this, unless there is another way of writing rewrite rules that I didn't find.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
During the CARTOFrames 🔱 project we've realized there are some annoying discrepancies between where files are on the CDN and when you load locally.
libs.cartocdn.com/airship-components/<version>/<file>
is
<hostname>:<port>/packages/components/dist/file
Even worse, on the CDN, it's airship-style, and locally it's styles.
Using serve we can add rewrite rules so you can write urls like:
<hostname>:<port>/airship-components/<version>/<path>
and rewrites to the correct file.
There's an open PR that we need for this, unless there is another way of writing rewrite rules that I didn't find.
The text was updated successfully, but these errors were encountered: