oliverpool

PS: I'm already doing some experiments with cobra: https://github.com/oliverpool/go-chromecast/tree/master/cmd/chromecast :-)

related to #3959 by @FredKSchott (reviewed by @matthewp and @tony-sull), who may have an opinion about this

@natemoo-re thank you for the feedback. Which solution do you think is the best? - add a trailing slash, when the URL should have one (not easy to implement, but...

> avoid a breaking change Since the current behavior (as of 1.0) is to have the paths without trailing slash on `astro build`, this would mean fixing the `astro serve`...

@matthewp I think everything is documented into my first post (with a Minimal Reproducible Example): > dev Astro.url.pathname should be matching what you typed into the browser It does. But...

Sounds good to me. A couple of remarks: - As far as I understand `trailingSlash` is only for the `dev server`. I don't see why it would impact `astro build`...

> we are not comfortable with changing the defaults now that 1.0 is out Too bad that this issue got attention after the 1.0 release (this issue was opened 2...

I have the same error message in a `.js` flle (and a local image). The `astro dev` runs fine, however the `astro build` fails.

I think I found my issue: I was using `getImage` at the top of my file, and not inside the `export const get = ...` function!

@firelizzard18 has done an extension which seems to supports the `tasks` of vs-code: https://marketplace.visualstudio.com/items?itemName=ethan-reesor.vscode-go-test-adapter Source code (MIT License): https://gitlab.com/firelizzard/vscode-go-test-adapter