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
Hey, this bug is back. My project is dead. I am on Meteor 1.4, running as a meteor project and updated cli with: npm i modulus@next -g
I was originally on an earlier version of meteor as a node instance, but that stopped working, so followed instruction. Now I am hosed with errors that look like the same as a few months back cor other users.
this is in console:
modulus deploy
Welcome to Modulus
You are logged in as ...
[?] Are you sure you want to use project q2? (yes)
Deploying Meteor version 1.4.1.1
Compressing project...
5.9 MB written
Uploading project...
Upload progress [===================] 100%
Deploying project into Meteor runtime...
Starting build.
Creating directories for build environment.
Downloading source.
Executing build.
Now using node v4.4.7 (npm v3.10.5)
Initializing Meteor environment.
Using [email protected].
Demeteorizing application...
=> Errors while initializing project:
While selecting package versions:
error: unknown package in top-level dependencies: streams
Conversion failed.
Build attempt failed, attempting again.
Starting build.
Creating directories for build environment.
Downloading source.
Executing build.
Now using node v4.4.7 (npm v3.10.5)
Initializing Meteor environment.
Using [email protected].
Demeteorizing application...
=> Errors while initializing project:
While selecting package versions:
error: unknown package in top-level dependencies: streams
Conversion failed.
Build attempt failed, attempting again.
Starting build.
Creating directories for build environment.
Downloading source.
Executing build.
Now using node v4.4.7 (npm v3.10.5)
Initializing Meteor environment.
Using [email protected].
Demeteorizing application...
[✓] q2 running at q2-46570.onmodulus.net
In the modulus console, I see this:
Now using node v0.10.41 (npm v3.10.8)
find: `./bundle/programs/server': No such file or directory
WARNING: No package.json file found.
ERROR: No start script found. There is no application to run.
The text was updated successfully, but these errors were encountered:
Hey, this bug is back. My project is dead. I am on Meteor 1.4, running as a meteor project and updated cli with: npm i modulus@next -g
I was originally on an earlier version of meteor as a node instance, but that stopped working, so followed instruction. Now I am hosed with errors that look like the same as a few months back cor other users.
this is in console:
modulus deploy
Welcome to Modulus
You are logged in as ...
[?] Are you sure you want to use project q2? (yes)
Deploying Meteor version 1.4.1.1
Compressing project...
5.9 MB written
Uploading project...
Upload progress [===================] 100%
Deploying project into Meteor runtime...
Starting build.
Creating directories for build environment.
Downloading source.
Executing build.
Now using node v4.4.7 (npm v3.10.5)
Initializing Meteor environment.
Using [email protected].
Demeteorizing application...
=> Errors while initializing project:
While selecting package versions:
error: unknown package in top-level dependencies: streams
Conversion failed.
Build attempt failed, attempting again.
Starting build.
Creating directories for build environment.
Downloading source.
Executing build.
Now using node v4.4.7 (npm v3.10.5)
Initializing Meteor environment.
Using [email protected].
Demeteorizing application...
=> Errors while initializing project:
While selecting package versions:
error: unknown package in top-level dependencies: streams
Conversion failed.
Build attempt failed, attempting again.
Starting build.
Creating directories for build environment.
Downloading source.
Executing build.
Now using node v4.4.7 (npm v3.10.5)
Initializing Meteor environment.
Using [email protected].
Demeteorizing application...
[✓] q2 running at q2-46570.onmodulus.net
In the modulus console, I see this:
Now using node v0.10.41 (npm v3.10.8)
find: `./bundle/programs/server': No such file or directory
WARNING: No package.json file found.
ERROR: No start script found. There is no application to run.
The text was updated successfully, but these errors were encountered: