babel-plugin-unassert | Babel plugin to encourage reliable programming
kandi X-RAY | babel-plugin-unassert Summary
kandi X-RAY | babel-plugin-unassert Summary
Babel plugin to encourage reliable programming by writing assertions in production code, and compiling them away from release.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of babel-plugin-unassert
babel-plugin-unassert Key Features
babel-plugin-unassert Examples and Code Snippets
Community Discussions
Trending Discussions on babel-plugin-unassert
QUESTION
I'm using a babel plugin to load environment variables from a .env
file into a React Native project, but changes to the .env
file are not loaded until the javascript file importing them changes. I'd like a way to tell the react-native packager to recompile in the event that this file changes. I would accept an answer that:
- Simply re-transpiles the entire project when a specific file (
.env
) changes. - Re-transpiles only those files containing a specific string, say
foo
Is there a simple way to do this by writing a plugin/middleware? Maybe a separate background script that fires events to watchman that the react-native packager is listening for?
[EDIT in reply to a comment]
My current .babelrc
is the following, where babel-plugin-react-native-config
is a plugin I wrote to do hot variable swapping in conjunction with the react-native-config
package.
ANSWER
Answered 2017-Feb-27 at 23:20Since it's been two weeks since I've asked this question, I'm going to post the (kind of terrible) workaround I was able to cobble together. I will leave this question unanswered, and accept any new answer that is better (less hacky) than this one.
The react native packager uses watchman
to watch for filesystem changes, and upon getting an event that some JS file has changed, it looks to see if the file has actually changed, and then retranspiles if so. This prevents me from doing something simple like a watchman trigger that touch
es the relevant JS file, because the react packager thinks it's so smart that it can ignore updates with no diff. Whatever.
So my solution is to create a watchman trigger on .env
changing which calls make clear_env_cache
, where clear_env_cache
is the following (phony) target in a Makefile
.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install babel-plugin-unassert
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page