-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
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
Is this package still being maintained? #124
Comments
@TimothyGu seems active but working on other projects :( |
/cc @ForbesLindesay We want to provide official supporting from webpack team to pug and move this repo to We need:
|
awesome stuff @alexander-akait |
Friendly ping @ForbesLindesay and @TimothyGu |
This would be great and give a little more piece of mind to everyone depending on this loader. Hope it gets migrated soon! |
No answer from developers 😞 |
I could have done it long ago |
Agreed this would be great. @alexander-akait - could the original developers be tracked elsewhere? For example LinkedIn or email (extracted from commits). |
@Rush I tried to connect using twitter, but no luck |
The current license suggests that moving it would be fine. Also it looks like it was originally maintained by someone else. The only downside to moving it is no-one will update this package and list it as unmaintained or to look for it at webpack-contrib. |
Written @ForbesLindesay in twitter DM again, maybe we will succeed |
He actually appears to be active on Github in general. I also sent him an email and linked this thread. |
@alubbe @bloodyowl @christopherdowson @droooney @ezhlobo @ForbesLindesay @hemanth @jbnicolai @leenty @LionNatsu @rlidwka @TimothyGu @tjconcept Is anyone here? Sorry for spam, I can not contact anyone |
@alexander-akait Sorry, I only created the logo. I've not worked with anyone on the project in a few years. |
I have npm permission, but I don't have github permission. If someone could give @alexander-akait or me admin access to this repo we could move it over or keep it here and allow someone to maintain it here. |
Any updates on this? |
And recently I had issues with |
I've added @sokra as an admin. I have had next to nothing to do with Pug and it's been years since I've been writing any serious amounts of HTML, although I still occasionally update a project using Pug. |
Thanks |
In the meantime - I forked and published simple-pug-loader - if anyone was having similar problems as me with this loader. |
Please don't ping me again if possible. I just did the logo in, like, 2016.
…On Sat, 13 Mar 2021, 15:05 Alexander Akait, ***@***.***> wrote:
Ping again @alubbe <https://github.com/alubbe> @bloodyowl
<https://github.com/bloodyowl> @christopherdowson
<https://github.com/christopherdowson> @droooney
<https://github.com/droooney> @ezhlobo <https://github.com/ezhlobo>
@ForbesLindesay <https://github.com/ForbesLindesay> @hemanth
<https://github.com/hemanth> @jbnicolai <https://github.com/jbnicolai>
@leenty <https://github.com/leenty> @LionNatsu
<https://github.com/LionNatsu> @rlidwka <https://github.com/rlidwka>
@TimothyGu <https://github.com/TimothyGu>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#124 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABRYQIC3H6K3542NZX6SO23TDN5M3ANCNFSM4J7KALPQ>
.
|
Likewise, not in this org anymore. |
@alexander-akait From the recent comments, it looks like @sokra was given repo permission a week or so ago, so he might be the one to coordinate with. |
I only have write access. I can't move or give anyone else access. |
@sokra Ah, that makes sense. In case it's helpful for tracking someone down to make the change, here's a way you can look up who's an admin: https://stackoverflow.com/questions/42538330/find-out-who-is-the-admins-for-a-git-repo/42539102 I did this with another repo earlier today, and it worked to just pass the endpoint to |
Ok here are the admins:
|
Hi, What do you think of alexander-akait's and sokra's offer of the webpack team supporting There have been some issues unaddressed for a while, particularly changing the version range of the
It's looking like you've added him with write privileges, but not as an admin. Would you be up for giving him admin access? Does there need to be more discussion between current admins first? |
Note that even with admin access I will only move this repo if there is an official "go" from the maintainers. |
I won't move it as I never got such mandate from the author. I think the suggestion for the webpack team to maintain it is great, if it's valuable to them. I see no reason they can't go ahead with that. |
I'm happy to move this package to webpack-contrib. I don't (unfortunately) have permission to create a repo in that org, so cannot do it right now. I'm also happy to add someone from the webpack team to the npm package. Please e-mail me ([email protected]) when you've given me permission to create repos in webpack-contrib. I'm also happy for any of the other maintainers to go ahead and move it if that's easier. P.S. sorry for the delayed response. I've been very focused on other projects this year, and had un-watched this repo as I don't personally use pug & webpack together on any projects and there were several other maintainers listed. |
@ForbesLindesay Done https://github.com/webpack-contrib/pug-loader and assigned you to admin |
I see the new repo is still not available yet. I wanted to open some issues and was wondering what the right place would be to work on this project. |
@ForbesLindesay Friendly ping |
did someone send him an e-mail? He probably won't receive / read notifications since he unwatched the repo etc? |
@alexander-akait Did you try emailing him? As m10 pointed out, it sounds like he doesn't have notifications enabled for this repo and instead asked you to email after setting up the necessary permissions. |
@noahbrenner yes, multiple times |
In case anybody is looking for a good alternative, I started using https://github.com/webdiscus/pug-loader (I am not affiliated!) which has great Webpack 5 support and reloading on every dependant file. And it even has multiple rendering modes. |
any update on this? is there some other way you can proceed with this? @ForbesLindesay seems unavailable..? |
Looks like https://github.com/webdiscus/pug-loader is good solution |
Correct. The latest version of webdiscus/pug-loader 1.7.1 even works well with webpack asset pipeline. I can |
Hello, I have released new version v2.2.0 of the pug-plugin. This plugin already contains the @webdiscus/pug-loader. Why the pug-plugin?
const PugPlugin = require('pug-plugin');
module.exports = {
entry: {
'index': './src/template/index.pug',
'about': './src/template/pages/about/index.pug',
// ...
},
plugins: [
new PugPlugin(),
],
module: {
rules: [
{
test: /\.pug$/,
loader: PugPlugin.loader,
},
],
},
// ...
};
link(href=require('./styles.scss') rel='stylesheet')
script(src=require('./main.js'))
<link href="/assets/css/styles.05e4dd86.css" rel="stylesheet">
<script src="/assets/js/main.f4b855d8.js"></script>
// resolve assets in imported package
@use 'material-icons';
// resolve webpack alias
@font-face {
font-family: 'Montserrat';
src: url('~Fonts/Montserrat/Montserrat-Regular.woff2'); //-> url(/assets/fonts/Montserrat-Regular.woff2)
}
// resolve relative path
.header {
background-image: url('../images/header.png'); //-> url(/assets/img/header.4fe56ae8.png)
}
You can see complete example here |
Hi!
I see that there aren't many stars but there are a lot of people using this package, but it has being a while since it was updated for the last time...
I'm using pug today and it's very useful in many cases, and I'm trying to use it with storybook but there's a flaw on this loader... I can't import a file that has a mixin on it. It always returns a empty template.
Man, that bug it's killing me... Please don't let this project die... It fells like there's no other option than those complicated framework out there... Pug is way better and simpler... please do not give up on this package... there are too many people using it...
The text was updated successfully, but these errors were encountered: