heroku-buildpack-webpack's People
Forkers
bkakadiya42 aguestuser goco-inc arronmabrey runlevel5 mattwalters ukasiu idris bletchley kirs tweettypography jamestyrrell marshall-lee experimentengine lemmycaution redbadger azevedo osamah railsnoob steos tkislan stranbury andrewjwu axiomzen sebryu metrox intey ideallical tdtds taskanalytics roostify kreativgebiet hekike pgangwani stibidik hellomd achreftlili team-murlocs dwinders maxbasque edcolcode tonydc humante intrueder bagasajah gabrielbauman david-mccullars bloomfire threadstudios sportsbitenews cubedevinc erlandsona carloslema averybross samuelralak eduhcosta healthsherpa helloworldhitech beyondwords-core jonathankolnik contrastapp prestonwpope boatpeoplebrtik 4naanheroku-buildpack-webpack's Issues
Add ---display-error-details flag to build
Webpack's error messages can be ambiguous at times. I suggest adding the display error details flag to the buildpack to assist in tracking down deployment errors.
Register with Buildpack Registry
My name is Jon Byrum and I’m a product manager at Heroku. Your buildpack is one of the top 200 most popular buildpacks on Heroku!
I would like to invite you to publish your buildpack early in our Buildpack Registry, before it is made available to the general public (expected early July).
To register your buildpack, visit: https://addons-next.heroku.com/buildpacks
Documentation: https://devcenter.heroku.com/articles/buildpack-registry
Why register?
- By registering early you’ll be able to grab your preferred namespace for the buildpack
- After registering, your buildpack will be available to all Heroku users when they run
heroku buildpacks:search
. In the future, we will only display registered buildpacks on elements.heroku.com/buildpacks - The Buildpack Registry makes it easy for you to publish a new version of your buildpack, as well as roll back if there are errors
Recommended naming conventions:
- We recommend that you use the same namespace (e.g., jbyrum) with Buildpack Registry that you use on GitHub
- In general, avoid using "buildpack" in the name of your registered buildpack
- For example: If your Github repo is github.com/foobar/heroku-buildpack-elixir, then we recommend a name like "foobar/elixir"
It would be greatly appreciated if you could publish before June 18th, as we prepare to make the feature publicly available. Registering a buildpack should take approximately 5 minutes.
If you have any questions about registering (or run into any issues), please email:
[email protected]
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.