0.3.2 • Published 4 years ago

@decode/client v0.3.2

Weekly downloads
-
License
MIT
Repository
-
Last release
4 years ago

Coming soon

Packaging and developing locally

For development purposes, you can use yarn link to have a local React app point to a local version of this project.

The only catch: You may run into the infamous error 13991 if you just yarn link this package alone.

Step 1

Instead, you'll need to yarn link this project and its copy of React, like this:

cd decode-client
yarn link
yarn install
cd node_modules/react
yarn link
cd YOUR_PROJECT
yarn link @decode/client
yarn link react

After following those steps, YOUR_PROJECT should be using the local copy of @decode/client.

(h/t: https://github.com/facebook/react/issues/14257#issuecomment-595183610)

Step 2

Whenever you make changes to @decode/client, you'll need to build it for it to be picked up by YOUR_PROJECT.

However, yarn build does an rm -rf dist/, which can crash a local dev server of eg Create React App. So instead, you can run:

yarn build-dev

This will not rm -rf dist/ first, but instead overwrite files with new ones. This may result in some strangeness over time. Eg, if you rename a file, I believe the old file will still stick around in dist/. So if you're seeing strangeness, just run yarn build.

0.3.2

4 years ago

0.3.1

4 years ago

0.3.0

4 years ago

0.2.6

4 years ago

0.2.5

4 years ago

0.2.4

4 years ago

0.2.3

4 years ago

0.2.2

4 years ago

0.1.21

4 years ago

0.1.22

4 years ago

0.1.23

4 years ago

0.2.1

4 years ago

0.2.0

4 years ago

0.1.20

4 years ago

0.1.18

4 years ago

0.1.19

4 years ago

0.1.17

4 years ago

0.1.16

4 years ago

0.1.14

4 years ago

0.1.15

4 years ago

0.1.13

4 years ago

0.1.11

4 years ago

0.1.12

4 years ago

0.1.10

4 years ago

0.1.8

4 years ago

0.1.9

4 years ago

0.1.7

4 years ago

0.1.6

4 years ago

0.1.5

4 years ago

0.1.4

4 years ago

0.1.3

4 years ago

0.1.2

4 years ago

0.1.1

4 years ago

0.1.0

4 years ago