You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please use this template to help contributors get a detailed description of the issue or feature.
For support questions, please use stackoverflow. This repository's issues are reserved for feature requests and bug reports.
1. Apply either the bug or feature-request label
feature-request
2. Describe the bug or feature
This suggestion comes from an issue that I faced on #531.
I tried replacing the npm variables in examples/package.json with the real value and it worked!
Now, this is just a suggestion, maybe instead of using the npm variables we'll just use the real value for cross OS compatibility? Or perhaps, add a documentation about it somewhere in the README.md.
I don't mind creating a PR for both solutions.
3. If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
For support questions, please use stackoverflow. This repository's issues are reserved for feature requests and bug reports.
1. Apply either the
bug
orfeature-request
labelfeature-request
2. Describe the
bug
orfeature
This suggestion comes from an issue that I faced on #531.
I tried replacing the npm variables in
examples/package.json
with the real value and it worked!Now, this is just a suggestion, maybe instead of using the npm variables we'll just use the real value for cross OS compatibility? Or perhaps, add a documentation about it somewhere in the
README.md
.I don't mind creating a PR for both solutions.
3. If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
Nope.
4. Please tell us about your environment:
The text was updated successfully, but these errors were encountered: