Closed jaydson closed 8 years ago
It looks like the documentation is wrong. I have everything working now, here's the steps:
npm install
npm run dev
npm link
Thoughts @UltCombo ?
I can confirm the build (npm test
/ npm run dev
) is failing, seems to be due to a bug in ESLint or babel-eslint. We can try updating these to latest, though I'd like to land these changes on es20xx simultaneously. In fact, I already have the latest ESLint working on an es20xx-generated project, I just have to apply these changes to es20xx and Harmonic.
The link
issue seems to be due to the failing build—as the build is failing, there is no dist
directory (which is where all the compiled code that is executed by Node resides).
So, fixing the documentation and updating es20xx will solve the problem, right?
I'll update our ESLint-related dependencies and migrate our .eslintrc
to the new version's format. That should fix the issue.
:+1:
I'm updating npm and doing a clean npm install
to make sure that the issue is fixed.
I've committed 77b6555c400b9fc93cdb34159c156366c5b90347, now npm run dev
should at least generate the dist
directory properly.
Though, I'm now getting a different error with ESLint:
Cannot find module 'babel-runtime/helpers/interop-export-wildcard'
I'm not sure if this is a problem with my installation, but at least it is not breaking the build.
@jaydson Can you check if the build is working for you?
You mean trying to build from zero again?
git pull && rm -rf node_modules && npm i
It worked.
Is ESLint working correctly for you?
The problem with ESLint was that npm@3's maximally flat dependencies tree was using an outdated babel-runtime
dependency for babel-eslint
due to our own babel-runtime
being outdated. This should fix it: 98f4486e8208bdda49c9c2c5a2ff36add3ff606c
I'm trying to build Harmonic and it's not working properly.
Node.js version: 5.4.0 npm version: 3.3.12 OS: Ubuntu 14.04
Steps to reproduce:
npm link
Thelink
command seems to work. But when I tried to run Harmonic on terminal, i have the following error:Then I tried to run
npm run dev
:I'm investigating this right now, but I want to keep the history here in case others have the same issue.