Open sandrosc opened 6 years ago
@alidcastano i tried build your site and i got this error:
ERROR Failed to compile with 1 errors 05:31:54
This dependency was not found:
- ~\content in ./.nuxt/plugins.markdownComponents.4f97e594.js
To install it, you can run: npm install --save ~\content
in plugins.markdownComponents.4f97e594.js:
importAllMdComps(
require.context("~\\content", true, /\.comp\.md$/)
)
the error stops when I change to:
importAllMdComps(
require.context("~/content", true, /\.comp\.md$/)
)
btw, content-api returns
"content-endpoints": [
"\\now",
"\\articles",
"\\projects"
]
I think that we could add some replaces, but i don't know where.
@sandrosc use Windows Subsystem for Linux to build your application now. ;)
@derevandal afaik the dependencies of his site are out of date, not sure if it's helpful for this bug.
@derevandal thx for the tip!
@sandrosc I got these error in my personal closed project too and here it works even with this dependency problem.
@derevandal @sandrosc Thanks for helping to narrow it down for me, ill try to find the time to update module for windows build and then do a quick update to this template as well
@alidcastano ok, if u need help and tell me what and where I should do, I can make a PR.
That's what I got when trying to run the examples/multiple-content-types
nuxt:render Rendering url /archives +29s nuxt:render Rendering url /content-api//posts/? +2ms { statusCode: 404, path: '/content-api//posts/?', message: 'This page could not be found' }
ERROR
Error: Request failed with status code 404
- createError.js:16 createError [multiple-content-types]/[axios]/lib/core/createError.js:16:15
- settle.js:18 settle [multiple-content-types]/[axios]/lib/core/settle.js:18:12
- http.js:192 IncomingMessage.handleStreamEnd [multiple-content-types]/[axios]/lib/adapters/http.js:192:11
- events.js:110 emitNone events.js:110:20
- events.js:207 IncomingMessage.emit events.js:207:7
- _stream_readable.js:1059 endReadableNT _stream_readable.js:1059:12
- next_tick.js:138 _combinedTickCallback internal/process/next_tick.js:138:11
- next_tick.js:180 process._tickCallback internal/process/next_tick.js:180:9
Multiple content types not working at all for me. I've read the docs several times. Everything works well until I change content to be an array instead of an object. Any solution for this?
@sebstr1 They don't work. Some claim on the development branch it works, but I used the nuxtdown module for now, which has this fixed and works without issues so far. You should be able to easily switch back to nuxtent in case it gets a patched release anytime soon.
@renestalder Thank you, I will look into that instantly!
@renestalder What OS are you using? I seem to have the same issue with nuxtent. Im on Windows 10. Works fine on my linux laptop.
Edit: I take some of that back. the content-api works only on linux. both the path and permalink generated in the content api results in 404
Edit2: The nuxtdown example for multiple content is also not working...
@sebstr1 Linux. (Arch)
@sebstr1 I didn't check the xamples at all. Just from the README, I could easily setup multiple content with nuxtdown after switching out the module in the nuxt configuration and changing the nuxtent tags in the Vue templates to nuxtdown.
Ok, after some more fiddeling I figured it out, working on my Linux machine! The same config does not work at all for Windows though.
We are working on Windows support. A workaround is to use the Linux subsystem on w10
Might be nice to insert a warning into the README to let people know that it doesn't work on Windows... rather than having people like me wasting hours and thinking it is something they misconfigured.
I tried to run several examples locally, some didn't work as soon as you click a link. The following is the output of the
multiple-content-types
example.I am on Windows 10, Node 9.3.