markdown-editor | default WordPress editor with a Markdown editor | Editor library

This is happening because you are including sectionID in the dependency list of the useEffect within EditorContainer. Because sectionID doesn't change on initial load, this useEffect never fires. I've created a minimal example of this here: https://codesandbox.io/s/focused-babbage-ilx4j?file=/src/App.js

I recommend changing useEffect to useMemo because it runs at least once on initial render of EditorContainer. And you still get the performance benefit because it shouldn't rerun unless sectionID changes.

Actual values are passed to context provider in App.js. Default context values are just safety mechanism in case someone will make consumer without provider.

Here is relevant documentation: https://reactjs.org/docs/context.html

Explanation:

It looks like you are missing a configuration for the markdown rules.

You can add a file in /src/lib/markdown, something like story.ts, with this content (copy/paste from notice.ts)

Using node_modules requires tools like Webpack. If your project is fully vanilla, you can try to add the cdn (I guess you need the links below), should work as npm module.

Easymde using module.exports, you can find it here So to use it in with yarn and rails 6 I think the way is in js file:

As we established in the comments section, your problem is not because of wrongly set up virtual environment, but it's worth mentioning the possible solution for others who might come across this question in future.

The problem with virtual env being invoked from other virtual env directory is a frequent symptom of copying virtual env directory from one place to another. This should be avoided! The reason behind that is the VIRTUAL_ENV variable hardcoded in [venv_dir]/bin/activate script. So, always make sure that this variable points to a valid directory.

In order to list packages from a virtual environment only, you need to use --local flag either for pip freeze or pip list. You can find this in the documentation:

-l, --local

If in a virtualenv that has global access, do not list globally-installed packages.

The key phrase is global access. The possible reason why pip keeps finding packages that are outside your virtual environment might be the PYTHONPATH and PATH environment variables. Check them. Whatever you have in those paths will be visible by pip.