How to build with a stable package name?
See original GitHub issueWhat is the current behaviour? Right now every
preact build
creates a random bundle hash in the dist folder.
What is the motivation or use case for changing this behaviour? I would like to have a stable filename in order to use it in docker build.
Describe the solution you’d like
preact build --file bundle.js
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
15.2. Building your First Package
The equivs-control file command creates a Debian package header file that should be edited to contain the name of the expected package, its...
Read more >Package authoring best practices - NuGet - Microsoft Learn
In Visual Studio, the recommended way to specify package metadata is to go Project > [Project Name] Properties > Package. Package metadata ...
Read more >Get Conan package name and version separately · Issue #2566
I've read the CONTRIBUTING guide. I've specified the Conan version, operating system version and any tool that can be relevant.
Read more >Arch package guidelines - ArchWiki
When building packages for Arch Linux, adhere to the package guidelines below, ... Maintainer: Your Name <youremail@domain.com> pkgname=NAME ...
Read more >Package naming conventions - Conda
Conda package names are normalized and they may contain only lowercase alpha characters, ... The package name, version, and build string joined together...
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
Closing this out now, figure we have covered all the bases.
Yeah you’re right, not using pre-rendering in my current project at the moment but with it it does indeed break on build, but adding the undefined check solves that issue. Thanks for adding the config for CSS files as well for the full overview!
Edit: without the undefined check running a dev environment through
preact watch
will also break on startup, so the undefined check is in necessary in al scenario’s.