thelarkinn

10 ms·

61.
by thelarkinn 10y ago
Ironically the biggest challenge is involved with connecting a very declarative under the hood plugin architecture, to a more imperitive fluid configuration for users. We would love all the great ideas we can get!
62.
by thelarkinn 10y ago
Thanks whoever posted this article!!! On behalf of the webpack core team, we thank everyone who's been using webpack 2 since beta, we are at the finish line for getting final release. :) stay tuned
63.
Webpack contributor spotlight: The first week of the year(medium.com)
11 points by thelarkinn 10y ago|0 comments
64.
by thelarkinn 10y ago
Awesome post!!! I'll reach out to our awesome-webpack companion repo and add this repo. Besides that, on behalf of the webpack core team, feel free and reach out if you have any other questions or want to get involved. We even have a n
65.
by thelarkinn 10y ago
Sorry to hear that was your experience, but also glad to hear you found a solution that works. If you do come back to trying webpack, we're happy to help get you up and running. Feel free to reach out on twitter or github @TheLarkInn
66.
by thelarkinn 10y ago
We have a plugin built around the research on HTTP/2 and web perf (which based on the data so far points to bundling still yielding the optimal results) called AgressiveSplittingPlugin. It's designed to allow you to specify a max
67.
by thelarkinn 10y ago
Well, as one of the maintainers besides working on core, and loaders/plugins, my role is to rep the voice of all of you to the core team, and also the other way around. Just here to help :)
68.
by thelarkinn 10y ago
Check the actual article and you'll see the v1-v2 migration link embedded into the post!!!
69.
by thelarkinn 10y ago
Do I have a github issue for you!!!! This is a feature tons of people ask for all the time so this week I officially marked it as RFC. https://github.com/webpack/webpack/issues/3466 Since the core team needs
70.
by thelarkinn 10y ago
We are really excited to work with Rich Harris on adding scope inlining, (Rollup'y) features. We were waiting to release 2 first :-D
71.
by thelarkinn 10y ago
Hey sorry this was your first (or many) experience(s). If I can be of any help, I'd recommend checking out our Concepts section which I authored for first-time users and those trying to understand the overall principles of loaders&#x2F
72.
by thelarkinn 10y ago
Also, if you find a plugin or a loader who is struggling to support or catch up, just drop us a message on github or tweet me at @thelarkinn, and myself or one of the other maintainers will offer to help or take over the plugin. We have a w
73.
by thelarkinn 10y ago
Well thank you for always being candid and honest with your feedback to us. We really rely on feedback from the community who is ultimately in charge of the direction of this incredibly humbling project. This goes to more than just you, but
74.
by thelarkinn 10y ago
No that was handwritten by Tobias the original author and I shared it on Twitter a few weeks back. We do have a lot of abstraction and complexity internally. But we like the direction and way it has allowed us to pivot toward and away new&#
75.
by thelarkinn 10y ago
Totally understand, now that webpack 2 is almost out the door, this is one of our top 5 overhauls we want to make. "Can we make smarter defaults" We support a lot of build targets and are agnostic to library and stack so it's
76.
by thelarkinn 10y ago
Thank you guys for the positive feed back. If you find anything quirky or just want to get involved, feel free and drop us a github issue. ️
77.
Webpack 2.2 – Release Candidate(medium.com)
197 points by thelarkinn 10y ago|86 comments
78.
by thelarkinn 10y ago
There is potentially a plugin that might work for you but an RFC on our core repo would be worth the time. Check out hard-source-webpack-plugin and see if that helps you.
79.
by thelarkinn 10y ago
Coming from a no-design-ux background, I never considered this and it would be a perfect issue on our github. Would you be interested in creating it? github.com/webpack/webpack.js.org/issues/new
80.
by thelarkinn 10y ago
Coming from a no-design-ux background, I never considered this and it would be a perfect issue on our github. Would you be interested in creating it? github.com/webpack/webpack.js.org/issues/new
81.
by thelarkinn 10y ago
Thanks for the thoughtful reply. I've created an issue for it so that we can discuss and plan where and what content should be added. https://github.com/webpack/webpack.js.org/issues/416 Also, if you wou
82.
by thelarkinn 10y ago
Have you checked out webpack.js.org/concepts. webpack.js.org is our entire new documentation effort designed initially for first time users. Take a look and feel free to submit an issue if there are things that are still confusing or y
83.
by thelarkinn 10y ago
We wanted to give influence to those who are involved in open source and contributing to the community. Would be happy to discuss alternative options.
84.
by thelarkinn 10y ago
DISCLAIMER: (dupe comment) This was an alpha feature that got leaked that we didn't expect to be circulated. Therefore we don't have UX/UI yet. We would love help and support so PR's, suggestions, issues are all welcome
85.
by thelarkinn 10y ago
Hey!!! This was an alpha feature that got leaked that we didn't expect to be circulated. Therefore we don't have UX/UI yet. We would love help and support so PR's, suggestions, issues are all welcome on github.com/w
86.
by thelarkinn 10y ago
By all means we take PR's as well. Our MVP list is pretty set in stone and we don't want to extend our timeline. However simply by adding the issue to the new docs repo, I'll make sure the information will get prioritized for
87.
by thelarkinn 10y ago
Rich couldn't have said better !!!!
88.
by thelarkinn 10y ago
Id recommend our newer upgrade guide. https://webpack.js.org/how-to/upgrade-from-webpack-1/
89.
by thelarkinn 10y ago
Id recommend our newer upgrade guide. https://webpack.js.org/how-to/upgrade-from-webpack-1/
90.
by thelarkinn 10y ago
I can understand your concerns but we made a promise early on that we wouldnt release v2 from beta until our MVP docs milestone is complete. We are just around 90% completion ( http://github.com/webpack/webpack.js.org&#x

More ›