How to generate output in same directory structure as src?
See original GitHub issueI’m wanting to convert a simple metalsmith site to run on deno, and Lume looks like a reasonable fit. One thing I’m stuck on is the structure of the output site. I want to convert src/abc.md
to site/abc.html
and src/xyz.md
to site/xyz.html
, but it puts each src file in its own directory, which I don’t want. I tried using the permalink
variable, but this makes no difference. Seems to be in site.js
but I can’t see any way to define this.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Output the same directory structure as the src #1736 - GitHub
I want to get the output in es/* to be same as src/* when building for es module system. What changes I have...
Read more >How to keep the source directory structure inside the output ...
You should be able to do either of these: path: path.resolve(__dirname, 'dist/js'),. or filename: 'js/[name].js',.
Read more >Download files and create same file structure as the source
I want to read the config file and and copy each URL but at the same time create the same directory structure as...
Read more >Customizing directory structure for generated code - IBM
Specifying the output directory for generated code · Open the Features window for the relevant component. · On the General tab, use the...
Read more >Working With Files - Gradle User Manual
The Project.file(java.lang.Object) method is used to create a file or directory path relative to the current project and is a common way to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
yay, that now works. Thanks for the lesson in using Deno. I see you can also use
-r
instead of--reload
, so a bit less to type.Moitas grazas (as you name your software with a Galician word, I assume you are galego 😃)
Yes, I didn’t find a good way to manage and update versioning. I’ve released
0.7.2
that fixes the problem with permalink. Updating a package is the same as installing it, but you need to add the-f
to force the installation (and override the previous installation), and--reload
to remove the cache and reload all dependencies:Note also that in
_config.js
you can return a lume instance of any version, different to what do you have installed in cli, for example:So, other way to update the version is just editing the version in the
_config.js
file.