Using assetPrefix for Custom Protocol
Unanswered
Cape May Warbler posted this in #help-forum
Cape May WarblerOP
Hey, so I made a somewhat-related post a while ago, but wanted to revisit the idea.
Basically, I'm trying to use nextjs as a GUI for VST Plugin development. The backend of the plugin is rust.
The idea is to export the app as static content and then request the content through a custom protocol registered on my plugin's backend.
I've gotten this to work with CRA, and now I'm trying to see if Nextjs will work. The config I've tried is:
However, when I try to compile everything and run my plugin, I get this in the console:
I can see that the protocol is working and delivering all of the assets (see the image attached).
What can I do to ignore this Invalid URL error, if there's any way? Thanks!!
Basically, I'm trying to use nextjs as a GUI for VST Plugin development. The backend of the plugin is rust.
The idea is to export the app as static content and then request the content through a custom protocol registered on my plugin's backend.
I've gotten this to work with CRA, and now I'm trying to see if Nextjs will work. The config I've tried is:
const nextConfig = {
output: 'export',
assetPrefix: 'http://webview.localhost/' //this is what a custom protocol url looks like on windows
};However, when I try to compile everything and run my plugin, I get this in the console:
TypeError: Failed to construct 'URL': Invalid base URL (everything does build correctly, it's a runtime issue)I can see that the protocol is working and delivering all of the assets (see the image attached).
What can I do to ignore this Invalid URL error, if there's any way? Thanks!!
1 Reply
Cape May WarblerOP
I would understand if ther e's no way to do this, considering my use case is a little strange