Closed emnul closed 1 month ago
Hey, thanks for reporting. Your issue helped me realize that turf wasn't providing enough information about the source of errors. I've created a new release that fixes this problem. By updating turf to 0.9.1
, you'll get more detailed error messages, which will make it easier to resolve the issue
Those new error messages helped me figure out the issue and fix it. However, in the README.md file it explains that the browser version formats can be defined as:
major |
---|
Use a single integer to specify the major version number. |
Example: 1 or [1] represent version 1.0.0 |
My project fails to build when I use the following configuration:
[package.metadata.turf.browser_targets]
chrome = [109]
but this works fine
[package.metadata.turf.browser_targets]
chrome = 109
Is this a bug with the settings parser?
This was indeed a bug in the settings parser. I resolved the issue in the latest release 0.9.2
. Thank you very much for reporting the issue!
I tried using turf in a leptos project, but my project fails to compile with the following error:
error: Could not obtain turf settings from the Cargo manifest
. Here's what myCargo.toml
file looks like:Everything seems to be configured fine, but I could be missing something.
In src/app.rs I have
At the top of the file, but Rust refuses to compile it