Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
🚀 Feature Request: Load values from wrangler.toml
See original GitHub issueDescribe the solution
A lot of times, I’d like my worker code to depend on some values I have in my wrangler.toml (e.g. getting the worker name, getting the routes it can be deployed to, etc.)
While I can duplicate this information in JS, it’d be easier if I could just import my wrangler.toml the same way I can import my package.json.
We should include a plugin to parse .toml files with esbuild (such as esbuild-plugin-toml so that wrangler publish can include imports from toml files.
Issue Analytics
- State:
- Created a year ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
We can currently achieve this via a custom build step, so I’m going to close this as not something we should implement in core Wrangler.
We should also be aware that the structure of a wrangler.toml is quite complex with all the inheritance options. So even if you imported this file directly, you might not be reading the correct values depending upon the current environment.